phi.de]
> Sent: Wednesday, September 23, 2009 1:42 AM
> To: java-dev@lucene.apache.org
> Subject: RE: NumericRangeQuery "static" constructors
>
> It is just for some type safety (with generics it would be better to
> handle). The problem is, that overloading the ctor with l
gersoll [mailto:gsing...@apache.org]
> Sent: Wednesday, September 23, 2009 1:33 AM
> To: java-dev@lucene.apache.org
> Subject: NumericRangeQuery "static" constructors
>
> I was wondering what was the reason for the "static" constructors on
> the NumericRangeQuery?
I was wondering what was the reason for the "static" constructors on
the NumericRangeQuery? I don't get the point of a static method call
that simply passes through to a normal constructor. Are people
somehow magically more capable of discerning the meaning of a static
method than simply
