SyntaxEditor 4.0 SyntaxLanguages - Need Input

SyntaxEditor for Windows Forms Forum

Posted 18 years ago by Actipro Software Support - Cleveland, OH, USA
One of the major new features in SyntaxEditor 4.0 is to be able to make programmatic lexical parsers for those developers who are advanced and want to optimize parsing speed. We've mocked up a simple programmatic lexical parser for C# that is optimized for C# text and can parse text in a fraction of the time of a SyntaxEditor 3.1 C# language definition.

Let's talk about the implementation. The SyntaxLanguage is now an abstract class that defines the base requirements for any language. Our mock programmatic C# language definition is in a class named CSharpSyntaxLanguage which inherits SyntaxLanguage. SyntaxLanguage defines a new lexical parsing method and in CSharpSyntaxLanguage, we override that method to use our programmatic lexical parser for C#. That lexical parser creates CSharpToken objects that are inserted into the Document's Tokens collection. And there is a CSharpTokenID enumeration that defines each keyword, operator, and other language element. Each CSharpToken has an ID property which correlates to a CSharpTokenID value.

So whereas in the SyntaxEditor 3.1 C# language definition, all keyword tokens had a key of KeywordToken, in SyntaxEditor 4.0 using this specialized CSharpSyntaxLanguage, each individual keyword has its own unique ID. This will make it easy to write semantic parsers that can build an object model and then support Intellisense features.

For those of you who like the 3.1-style languages, we are still going to support the 3.1 style languages via an implementation of SyntaxLanguage. We aren't sure yet what to call that implementation class and are hoping you can vote which name you prefer by replying here or coming up with another name you like.

Some names that we came up with for the 3.1-style language implementation are:

Which do you like best? We like the first two best.

3.1-style languages are nice because they are easily customizable whereas the languages with programmatic implementations of lexical parsers will be hardcoded and rigid, but very fast.

If you have any other questions about some changes/enhancements for languages and tokens, post them here.

Actipro Software Support

Comments (6)

Posted 18 years ago by Boyd - Sr. Software Developer, Patterson Consulting, LLC
I vote for DynamicSyntaxLanguage
Posted 18 years ago by Eric J. Smith - CodeSmith Tools, LLC
I vote for DynamicSyntaxLanguage as well.
Posted 18 years ago by NSXDavid
Whatever you call it.... very cool. ;)
Posted 18 years ago by Devin Grant - Novi
DynamicSyntaxLanguage sounds good!
Posted 18 years ago by Jean Versailles
DynamicSyntaxLanguage it is.
Posted 18 years ago by Marianne
One key for me is getting to information that the user has changed, either via keystroke, cut/copy/paste, etc. What would be nice is to receive a array(s) depending on the operation. For example, although there is a DeletedTokens[] array property it would be good to add InsertedTokens[] and ModifiedTokens[] arrays it would be easier to maintain state on these various operations, not just for Intellisense but for all other operations that depend on the state of these tokens. As it is now, I need to get a text stream and basically rebuild this information for it to be useful to me. It would be good if it were somehow provided.

------------------------------- Marianne

The latest build of this product (v24.1.0) was released 4 months ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.