[Lxr-dev] [ lxr-Feature Requests-2755517 ] Support case-insensitive languages

[SourceForge.net <no...@so...>]

Feature Requests item #2755517, was opened at 2009-04-12 12:04
Message generated for change (Comment added) made by adrianissott
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2755517&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Language support
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: AdrianIssott (adrianissott)
>Assigned to: AdrianIssott (adrianissott)
Summary: Support case-insensitive languages

Initial Comment:
This feature would make LXR better suited to at least the following languages:
* Pascal (fully case-insensitive)
* Visual Basic (fully case-insensitive)
* SQL (partially case-insensitive - reserved words are CI but table / columns names may not be)
* PHP (partially case-insensitive - fn / class names are CI but variable names aren't)

Two particular issues to keep in mind are:
* It's too simplistic to assume languages are either case-sensitive or not.
* Allowing searches to be case-insensitive (e.g. for identifiers) will increase the number of false positives returned (i.e. matches that the user doesn't care about) and make searching less useful.

I propose this feature is implemented in the following stages:
1) Feature Request 2755445 Language Specific Searches to mitigate the issue of increased false positives when searching by allow case-insensitive searches to be restricted to just those languages in which it makes sense. See https://sourceforge.net/tracker/?func=detail&aid=2755445&group_id=27350&atid=390120 for more details.
2) The format of generic.conf should be updated to allow case-insensitivity to be specified per language as follows:

    'caseinsensitivity' => {
        'reserved' => [01],
        'type_a'    => [01],
        'type_b'    => [01],
        ...
    },
  
    Where type_a, type_b etc are the types listed in the typemap for the language.
3) Add the case-insensitivity functionality for reserved words when locating them for mark up in source files being browsed (has no impact on searching).
4) Add the case-insensitivity functionality per type when locating symbols for mark up in source files being browsed.
5) Add the case-insensitivity functionality per type when adding links to identifier searches in source files being browsed.
6) Allow identifier searches to be specified as case-insensitive by the user. [Don't try to do anything fancy such as preset this according to what languages the search is restricted to].
7) Ensure general searches on file contents can be made case insensitive by the user.

----------------------------------------------------------------------

>Comment By: AdrianIssott (adrianissott)
Date: 2009-04-12 12:05

Message:
Will fix bug 1832713 Implement case-insensitive language processing.

See
https://sourceforge.net/tracker/index.php?func=detail&aid=1832713&group_id=27350&atid=390119

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390120&aid=2755517&group_id=27350