We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
status NEW severity minor in component indexer for --- Reported in version unspecified on platform ANY/Generic Assigned to: Trond Norbye
On 2009-09-18 18:19:25 +0000, Zach Carter wrote:
Given a hex number like 0x21600000, You cannot search for 2160* to find it. These queries work: x2160* 0x21600000 However, these do not: 0x2160* 2160*
Given a hex number like 0x21600000, You cannot search for 2160* to find it.
These queries work:
x2160* 0x21600000
However, these do not: 0x2160* 2160*
On 2010-06-22 14:26:31 +0000, Lubos Kosco wrote:
I accidentally stumbled upon this bug again and it seems it might be the way how we index numbers in plainanalyzer is not the best ... see http://src.opensolaris.org/source/xref/opengrok/trunk/src/org/opensolaris/opengrok/analysis/plain/PlainFullTokenizer.lex# 60 the regexp is not that great Zach, any chance to update this bug with type of language where it happens ? thanks L
I accidentally stumbled upon this bug again and it seems it might be the way how we index numbers in plainanalyzer is not the best ...
see http://src.opensolaris.org/source/xref/opengrok/trunk/src/org/opensolaris/opengrok/analysis/plain/PlainFullTokenizer.lex# 60
the regexp is not that great
Zach, any chance to update this bug with type of language where it happens ?
thanks L
The text was updated successfully, but these errors were encountered:
No branches or pull requests
status NEW severity minor in component indexer for ---
Reported in version unspecified on platform ANY/Generic
Assigned to: Trond Norbye
On 2009-09-18 18:19:25 +0000, Zach Carter wrote:
On 2010-06-22 14:26:31 +0000, Lubos Kosco wrote:
The text was updated successfully, but these errors were encountered: