From 7434ebca8b4467adf800f0943d0dd2d6bd11cee9 Mon Sep 17 00:00:00 2001 From: nyamatongwe Date: Sun, 6 Jul 2008 04:48:25 +0000 Subject: Explanations about regular expression replacement. --- doc/ScintillaDoc.html | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) (limited to 'doc/ScintillaDoc.html') diff --git a/doc/ScintillaDoc.html b/doc/ScintillaDoc.html index 1f3e43a3d..ca14293a9 100644 --- a/doc/ScintillaDoc.html +++ b/doc/ScintillaDoc.html @@ -515,7 +515,10 @@ struct TextRange {

Searching

There are methods to search for text and for regular expressions. The regular expression support - is limited and should only be used for simple cases and initial development. + is limited and should only be used for simple cases and initial development. A different regular expression + library can be integrated into Scintilla + or can be called from the container using direct access to the buffer contents through + SCI_GETCHARACTERPOINTER.

SCI_FINDTEXT(int flags, TextToFind *ttf)
@@ -5611,6 +5614,16 @@ EM_SETTARGETDEVICE following the patterns of other lexers. The important thing is to include LINK_LEXER(lmMyLexer); to correspond with the LexerModule lmMyLexer(...); in your lexer source code.

+ +

Building with an alternative Regular Expression implementation

+ +

A simple interface provides support for switching the Regular Expressions engine at + compile time. You must implement RegexSearchBase for your chosen engine, + look at the built-in implementation BuiltinRegex to see how this is done. + You then need to implement the factory method CreateRegexSearch + to create an instance of your class. You must disable the built-in implementation by defining + SCI_OWNREGEX.

+ -- cgit v1.2.3