Joerg  Schneider:

I had some problems getting it linked. To resolve undefined symbols I had
to add the following file from a scintilla\win32 directory:

WindowAccessor.obj PropSet.obj PlatWin.obj XPM.obj UniConversion.obj

Is this the normal way to link external lexers?

If yes, wouldn't it be nicer to export the required symbols from
scilexer.dll or a separate DLL, which comes with Scintilla?

  The intention was to not require any direct linkage to Scintilla,
hence isolating external lexers from changes in internal classes. Each
of the 4 functions receives flattened 'C' compatible arguments rather
than pointers to classes. You may use Scintilla classes in your
implementation but it should also be possible to implement a lexer in
C or Delphi.

  I don't see much reason for distributing external lexers. If you
are distributing an application that incorporates Scintilla you should
be releasing a tested set of Scintilla and lexers. Static linking
produces more efficient code and there is less to go wrong.

  Neil
_______________________________________________
Scintilla-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scintilla-interest

Reply via email to