RE: GNU Global Parsing Suffixless Files Patch

[Cooper, Anthony]

SECURITY CLASSIFICATION: OFFICIAL 


Good morning :-) (See comments below)

> -----Original Message-----
> From: address@hidden [mailto:address@hidden On Behalf Of 
> Shigio YAMAGUCHI
> Sent: 01 October 2016 00:17
> To: Cooper, Anthony
> Cc: address@hidden
> Subject: Re: GNU Global Parsing Suffixless Files Patch
> 
> Before implementation, I would like to make clear the specification.
> 
> > Assorted projects I've come across have include and Include (the 
> > example below is a trivial but a real one relating to MS-Windows) 
> > and some even have include dirs names XInclude or something similar 
> > (can't remember the project now, wasn't X11 but probably an X client).
> 
> Let me ask a couple of questions, please.
> 
> 
> Q1: Is the following (1) and (2) equal?
> 
>         (1) --language-force='cpp:([Ii]nclude)'
>         (2) --language-force='cpp:include' --language-force='cpp:Include'
> 
>     If so, you think that (1) is better than (2) since it is shorter?

Yes precisely. Although perhaps I gave a rather weak example. A stronger case 
would be when differentiating between say:
        /usr/include/C++/4.8/algorithm
        /usr/include/C++/5.1/algorithm
        /usr/include/C++/..../algorithm
And:
        ./project/helper-programs/algorithm/sort/qsort  <- script or binary

Or to match:
        .../include/sys
But not:
        .../include/system_errors

If I wanted to catch the first set of files in both example without tripping up 
over the second then I could do --language-force=cpp:(algorithm\$)  and 
--language-force=cpp:(sys\$).

> 
> Q2: Does (1) above match to the followings?
> 
>         ./XXXincludeYYY/
>         ./XXXincludeYYY.php
>         ./project/include/release/
>         ./project/include/release/test.php

Yes. The matching is a dumb substring or regex match on the path string 
available around where decide_lang() is called. No anchoring by default. 

> 
> Q3: Regex '^' and '$' are available? If so, what does they mean?

Yes they are. `^' would mean start matching at the beginning of the path and 
`$' would mean match the end of the path (particularly useful for just picking 
up matches against a file name as directories in themselves aren't processed 
beyond traversal). File globbing doesn't make ^ and $ available and I have come 
across other programs/situations where I have been frustrated by this for want 
of a regex. E.g. If I had:
        Default: \
        :GTAGS_OPTIONS=--force-language=yacc\:(sys\$): \
                               --force-language='cpp\:(^\\./Microsoft Visual)':
Then this would say match all files ending in sys and treat them as yacc and 
any suffixless files with a path starting with `./Microsoft Visual' are to be 
treated as cpp files.

One thing to note, made in the man page and help text, is this switch won't 
affect any files with a suffux, which some people might expect with `force' in 
the name of the switch.

Did you correctly receive the new patch for 6.5.5?

Many thanks once again :-).

Regards Tony.
> 
> Regards,
> Shigio
> 
> --
> 
> Shigio YAMAGUCHI <address@hidden>
> PGP fingerprint: D1CB 0B89 B346 4AB6 5663  C4B6 3CA5 BBB3 57BE DDA3
> 
> 
> __________________________________________________________
> ____________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com 
> __________________________________________________________
> ____________


****************************************************************************
Communications with GCHQ may be monitored and/or recorded 
for system efficiency and other lawful purposes. Any views or 
opinions expressed in this e-mail do not necessarily reflect GCHQ 
policy.  This email, and any attachments, is intended for the 
attention of the addressee(s) only. Its unauthorised use, 
disclosure, storage or copying is not permitted.  If you are not the
intended recipient, please notify address@hidden  

This information is exempt from disclosure under the Freedom of 
Information Act 2000 and may be subject to exemption under
other UK information legislation. Refer disclosure requests to 
GCHQ on 01242 221491 ext 30306 (non-secure) or email
address@hidden

****************************************************************************