Neil Hodgson wrote:
Piotr Fusik:
Matching shouldn't be too easy as many files include other language
names in header comments.
Examples?
Please note that I gave the example of "/perl" pattern for shbang header for
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.
# Basic settings and modes not yet moed into individual files
Properties file, not Basic
What header for Basic should be recognized?
# Define SciTE settings for Lua files.
Properties file, not Lua
What header for Lua should be recognized?
# IFaceTableGen.py - regenerate the IFaceTable.cxx from the Scintilla.iface
Python, nots C++
# Make file for SciTE on Windows Visual C++ and Borland C++ version
Make file, not C++
# The construction file for SinkWorld Java
Construction file, not Java
# jam for SinkWorld text cxx
Jam file, not C++
#include "Python.h"
C++, not Python
Don't use first-line matching for C++.
#~ command.build.*.cxx=scons.bat .
Properties file, not C++ or Batch
Neither for batch files.
/* gmarkup.h - Simple XML-like string parser/writer
C, not XML
XML should be matched by the "<?xml " pattern.
/* type macros, generated by maketypes.awk */
C, not Awk
The patterns for Awk are probably "/awk", "/gawk" or sth like this
(I have no experience with Awk).
// Not generated from C++
Java, not C++
No first-line matching for C++.
<[EMAIL PROTECTED]>
HTML/ASP, not Javascript
That's obviously ASP ("<%@").
Lua License
Text, not Lua
What header for Lua should be recognized?
import java.awt
Python (Jython), not java
No first-line matching for Java.
Piotr
_______________________________________________
Scite-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scite-interest
