Migrate from GitHub to SourceForge with this tool. Check out all of SourceForge's recent improvements.
Close

#933 Lexer for OScript language

closed
Scintilla (358)
5
2012-06-01
2012-05-03
No

OScript is a VB-like proprietary language used by the Livelink application server (http://www.greggriffiths.org/livelink/development/oscript/). 99 Bottles in OScript: http://99-bottles-of-beer.net/language-oscript-526.html.

A couple of my colleagues with me often use SciTE to look at or edit source files opened from filesystem or perforce. Although OScript is usually edited in Livelink Builder (IDE), SciTE is a good companion. I'm thinking about integrating Scintilla into the Builder which lacks syntax highlighting today.

Discussion

  • Ferdinand Prantl

    the attached archive contains full patch against 3.1.0 or complete files with changes.

     
  • Neil Hodgson

    Neil Hodgson - 2012-05-04
    • assigned_to: nobody --> nyamatongwe
     
  • Neil Hodgson

    Neil Hodgson - 2012-05-06

    g++ and clang have some warnings:
    ../lexers/LexOScript.cxx: In function 'bool IsAlpha(int)':
    ../lexers/LexOScript.cxx:39:54: warning: suggest parentheses around '&&' within '||' [-Wparentheses]
    ../lexers/LexOScript.cxx: In function 'bool IsNumberChar(int, int)':
    ../lexers/LexOScript.cxx:64:53: warning: suggest parentheses around '&&' within '||' [-Wparentheses]
    ../lexers/LexOScript.cxx: In function 'void FoldOScriptDoc(unsigned int, int, int, WordList**, Accessor&)':
    ../lexers/LexOScript.cxx:475:63: warning: suggest parentheses around '&&' within '||' [-Wparentheses]

     
  • Ferdinand Prantl

    Replacement LexOScript.cxx with no warnings in GCC. Replacement oscript.properties ready for API autocomplete and calltips. New oscript.api.

     
  • Ferdinand Prantl

    Fixed. (I'm bewildered that GCC warns about correct syntax and so makes operator precedence rules needless...) No warnings in MSVC and MinGW/GCC now.

     
  • Ferdinand Prantl

    Thanks. I have three versions of the API with diffent amount of text. I'm going to post them there.

     
  • Ferdinand Prantl

    Attention: I noticed that I made a mistake in the file extension. Could you, please, replace "ocx" with "osx" in oscript.properties and SciTEGlobal.properties? The correct extension is "osx". I'm sorry...

     
  • Neil Hodgson

    Neil Hodgson - 2012-05-19

    OK, updated to "osx".

     
  • Neil Hodgson

    Neil Hodgson - 2012-05-28

    Updated properties file to rename keywordclass.control to keywordclass.oscript.control as keywordclass.control was used in powerpro.properties.

     
  • Neil Hodgson

    Neil Hodgson - 2012-06-01
    • status: open --> closed
     

Log in to post a comment.