[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Match/Context naming

Depending on what we decide on, this will effect the recent changes to the CategoryPublisher application. Here I used the terms context and match to describe the type of _expression_ for an IU query in the category.xml [1] [2].

I agree that context seems like a strange term but I'm not sure I don't have any better suggestions.


[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=303127
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=303128

Inactive hide details for Thomas Hallgren ---02/23/2010 12:09:25 PM---Hi,Thomas Hallgren ---02/23/2010 12:09:25 PM---Hi,


Thomas Hallgren <thomas@xxxxxxx>


P2 developer discussions <p2-dev@xxxxxxxxxxx>


02/23/2010 12:09 PM


[p2-dev] Match/Context naming

Before I did the latest refactoring, the _expression_ equivalent for a
context query was named QLContextQuery and resided in the QL package.
For various reasons, I had to move that to the metadata package instead.
I then renamed it ExpressionContextQuery. So now we have ExpressionQuery
and ExpressionContextQuery. The former implements IMatchQuery and thus
expects a boolean _expression_ to be applied on each row. The latter is a
full query that is applied on all rows.

I'm not at all happy with the names. Both queries are _expression_
queries. And the term 'context' strikes me as a bit odd. What context?
The evaluation context? Query context?

The term 'match' is better. The each candidate is matched against a
boolean _expression_. But I would really like two terms that are related.
'match' and 'context' has no relationship. How about 'each' and 'all' ? I.e.

ExpressionQuery (common super)

Do you have suggestions? I'd like to hear them.

Thomas Hallgren

p2-dev mailing list

GIF image

GIF image