Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#959 Structured Text lexer support.

Completed
closed
Neil Hodgson
4
2013-06-02
2012-10-15
Pavel
No

Hi!
I\'ve implemented a new lexer for language Structured text. Details description, syntax and other necessary info you can find here - http://en.wikipedia.org/wiki/Structured_text

In attached there is a lexer source file, modified header "Scintilla.h" and modified file for processing Python compiler. I've checked this lexer with scintilla version 3.2.2. Is it possible to include this lexer into future releases of scintilla ?

Discussion

1 2 > >> (Page 1 of 2)
  • Pavel
    Pavel
    2012-10-15

    FIles

     
    Attachments
  • Neil Hodgson
    Neil Hodgson
    2012-10-16

    • assigned_to: nobody --> nyamatongwe
     
  • Neil Hodgson
    Neil Hodgson
    2012-10-16

    I won't be looking at this until next year.

     
  • Neil Hodgson
    Neil Hodgson
    2012-12-30

    Fails to build:
    ..\lexers\LexSTTXT.cxx(155) : error C3861: 'ClassifyfcSTWord': identifier not found
    ..\lexers\LexSTTXT.cxx(184) : error C3861: 'ClassifyfcSTWord': identifier not found
    ..\lexers\LexSTTXT.cxx(379) : error C3861: 'ClassifyfcSTWordFoldPoint': identifier not found

    In the Scintilla.iface file, there should be '=' between the symbol and value for 'val' lines.

     
  • Neil Hodgson
    Neil Hodgson
    2012-12-30

    • priority: 5 --> 4
     
  • Pavel
    Pavel
    2013-04-19

    Sorry!
    Chacked with scintiila331 ver.

     
    Attachments
    • Neil Hodgson
      Neil Hodgson
      2013-04-19

      C:\u\hg\scintilla\lexers\LexSTTXT.cxx:306 Summary: Same expression on both sides of '||'.

       
      • Pavel
        Pavel
        2013-04-19

        Error during compilation? If yes, what compiler do you use ?

         
        • Neil Hodgson
          Neil Hodgson
          2013-04-19

          Its not an error: its a bug with a repeated expression probably showing that a case was missed.

          I check with Visual C++. g++ and Clang. Also run cppcheck and the analyze commands of Visual C++ and Clang.

          The file needs a header comment pointing to the License.txt similar to LexPython.cxx.

          The name "fcST" does not produce any reasonable hits on Google so appears to be a poor choice.

           
  • Pavel
    Pavel
    2013-04-30

    Updated, added copyrights info & renamed. See attachment.

     
    Attachments
1 2 > >> (Page 1 of 2)