Piotr Fusik:
> Please note that I gave the example of "/perl" pattern for shbang header for
> perl.
The #! idiom often uses "/usr/bin/env" before the name of the
interpreter. For example, "#!/usr/bin/env perl".
> > "bin\boost\libs\python\build\boost_python.dll\vc-7_1\debug\threading-multi\numeric.obj"
> >
> > Command file, not python
>
> "/python" doesn't match it.
"/python" doesn't match this start line:
#!/usr/bin/env python
> > # Basic settings and modes not yet moed into individual files
> > Properties file, not Basic
>
> What header for Basic should be recognized?
#!/usr/bin/basic or #!/usr/bin/env basic are rare but used by some.
Your statement was "I think that any sequence of characters should
be matched anywhere in the first line". I'm pointing out that that is
not going to work for many files. I want it to be harder to start to
match ensuring fewer incorrect matches.
> What header for Lua should be recognized?
#!/usr/bin/env lua
Or reasonable variants. You can add options or point to a copy you
compiled into a private area.
> Don't use first-line matching for C++.
> Neither for batch files.
> No first-line matching for Java.
Why not? I wouldn't mind C++ headers without extensions like the
standard string, vector, ... styling nicely.
> > /* gmarkup.h - Simple XML-like string parser/writer
> > C, not XML
>
> XML should be matched by the "<?xml " pattern.
So its a special case.
> > <[EMAIL PROTECTED]>
> > HTML/ASP, not Javascript
>
> That's obviously ASP ("<%@").
Or a JSP directive.
Neil
_______________________________________________
Scite-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scite-interest
