Lexilla metadata

Neil <[email protected]> Tue, 17 Mar 2026 17:19:18 -0700 (PDT)
Newsgroups gmane.comp.lib.scintilla.devel
Message-ID <[email protected]>
------=_Part_24466_54434747.1773793158922
Content-Type: multipart/alternative; 
	boundary="----=_Part_24467_428259090.1773793158922"

------=_Part_24467_428259090.1773793158922
Content-Type: text/plain; charset="UTF-8"

Some new metadata features have been committed to Lexilla in the 
test/Metadata directory.

A C++ program 'Metadata' will load a given Lexilla shared library, 
instantiate each lexer, and print out the results from the metadata calls. 
This includes the keyword lists, options and styles supported by each lexer 
when that lexer provides metadata through calls. Old-style function lexers 
provide less metadata. Metadata can be built with gcc or clang with the 
provided makefile. There are instructions for building with Visual C++ in 
the source.

A file test/Metadata/lexerMetadata.txt contains the results of running the 
Metadata program on the standard Lexilla shared library in bin.

The resulting text can be viewed by users or processed by scripts that want 
to generate styling configuration files or dialogs. If projects would like 
this to be formatted into YAML, JSON, or similar, that could be an option 
to Metadata.

Running 'Metadata -check` checks that the Lexilla shared library in bin 
produces the same output as lexerMetadata.txt, then exits with a failure 
status and produces lexerMetadata.txt.new with the new results if they 
differ. This will be used to ensure there are no regressions from changes 
to Lexilla and that any changes are consistent.

A python program test/Metadata/CheckMeta.py checks for consistency between 
include/LexicalStyles.iface, test/Metadata/lexerMetadata.txt, and lexer 
source code files lexers/Lex*.cxx.

Neil

-- 
You received this message because you are subscribed to the Google Groups "scintilla-interest" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion visit https://groups.google.com/d/msgid/scintilla-interest/433420f6-5fe5-4f69-a53b-87ddf9aa8ef1n%40googlegroups.com.

------=_Part_24467_428259090.1773793158922
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Some new metadata features have been committed to Lexilla in the test/Metad=
ata directory.<div><br /></div><div>A C++ program 'Metadata' will load a gi=
ven Lexilla shared library, instantiate each lexer, and print out the resul=
ts from the metadata calls. This includes the keyword lists, options and st=
yles supported by each lexer when that lexer provides metadata through call=
s. Old-style function lexers provide less metadata. Metadata can be built w=
ith gcc or clang with the provided makefile. There are instructions for bui=
lding with Visual C++ in the source.</div><div><br /></div><div>A file test=
/Metadata/lexerMetadata.txt contains the results of running the Metadata pr=
ogram on the standard Lexilla shared library in bin.</div><div><br /></div>=
<div>The resulting text can be viewed by users or processed by scripts that=
 want to generate styling configuration files or dialogs. If projects would=
 like this to be formatted into YAML, JSON, or similar, that could be an op=
tion to Metadata.</div><div><br /></div><div>Running 'Metadata -check` chec=
ks that the Lexilla shared library in bin produces the same output as lexer=
Metadata.txt, then exits with a failure status and produces lexerMetadata.t=
xt.new with the new results if they differ. This will be used to ensure the=
re are no regressions from changes to Lexilla and that any changes are cons=
istent.</div><div><br /></div><div>A python program test/Metadata/CheckMeta=
.py checks for consistency between include/LexicalStyles.iface, test/Metada=
ta/lexerMetadata.txt, and lexer source code files lexers/Lex*.cxx.</div><di=
v><br /></div><div>Neil</div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;scintilla-interest&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:[email protected]">=
[email protected]</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/d/msgid/=
scintilla-interest/433420f6-5fe5-4f69-a53b-87ddf9aa8ef1n%40googlegroups.com=
?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/=
scintilla-interest/433420f6-5fe5-4f69-a53b-87ddf9aa8ef1n%40googlegroups.com=
</a>.<br />

------=_Part_24467_428259090.1773793158922--

------=_Part_24466_54434747.1773793158922--