VHDL Block Comment /* */ support in SciLexerVHDL

Hi,
I was wondering if this is supported? Right now block comment doesn't
change color in VHDL file.
If i need to enable this for VHDL_2008 is there anyway i can do it?
thanks

--

-- 
You received this message because you are subscribed to the Google Groups "scintilla-interest" group.
To post to this group, send email to scintilla-interest <at> googlegroups.com.
To unsubscribe from this group, send email to scintilla-interest+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/scintilla-interest?hl=en.

Re: VHDL Block Comment /* */ support in SciLexerVHDL

On 02/03/2010 03:35, chanhuai wrote:
> I was wondering if this is supported? Right now block comment doesn't
> change color in VHDL file.
> If i need to enable this for VHDL_2008 is there anyway i can do it?

You asked that a month ago, in the context of QsciLexerVHDL (not sure what it is, perhaps 
a build to use with Qt?).
I suppose we hoped that VHDL's lexer writer or somebody interested in maintaining it would 
answer/fix that. Looks like nobody reacted...

I looked at LexVHDL.cxx, the lexer itself is quite simple (the folding code is much more 
complex!).
If you don't mind lack of folding of block comments, it should be easy to patch the lexer. 
Can you compile that file yourself, to integrate it to your environment?

-- 
Philippe Lhoste
--  (near) Paris -- France
--  http://Phi.Lho.free.fr
--  --  --  --  --  --  --  --  --  --  --  --  --  --

--

-- 
You received this message because you are subscribed to the Google Groups "scintilla-interest" group.
To post to this group, send email to scintilla-interest <at> googlegroups.com.
To unsubscribe from this group, send email to scintilla-interest+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/scintilla-interest?hl=en.

Re: VHDL Block Comment /* */ support in SciLexerVHDL

Hi Philippe,
Thanks for replying.
Yes, QsciLexerVHDL is the qt version of LexVHDL.
I can compile the file and integrate it to my environment if there's a
patch.
Would appreciate your help. :)

On Mar 2, 4:54 pm, Philippe Lhoste <Phi... <at> GMX.net> wrote:
> On 02/03/2010 03:35, chanhuai wrote:
>
> > I was wondering if this is supported? Right now block comment doesn't
> > change color in VHDL file.
> > If i need to enable this for VHDL_2008 is there anyway i can do it?
>
> You asked that a month ago, in the context of QsciLexerVHDL (not sure what it is, perhaps
> a build to use with Qt?).
> I suppose we hoped that VHDL's lexer writer or somebody interested in maintaining it would
> answer/fix that. Looks like nobody reacted...
>
> I looked at LexVHDL.cxx, the lexer itself is quite simple (the folding code is much more
> complex!).
> If you don't mind lack of folding of block comments, it should be easy to patch the lexer.
> Can you compile that file yourself, to integrate it to your environment?
>
> --
> Philippe Lhoste
> --  (near) Paris -- France
> --  http://Phi.Lho.free.fr
> --  --  --  --  --  --  --  --  --  --  --  --  --  --

Re: VHDL Block Comment /* */ support in SciLexerVHDL

On 03/03/2010 02:19, chanhuai wrote:
> I can compile the file and integrate it to my environment if there's a
> patch.

OK, here is a quick hack.
In SciLexer.h, you have to add the line:

#define SCE_VHDL_BLOCKCOMMENT 15

preferably after the SCE_VHDL_USERWORD definition.
Of course, in your vhdl.properties file, you add:

# Block comments
style.vhdl.15=$(colour.code.comment.box),$(font.code.comment.box)

or something similar (your choice of style).

Now, just add the lines:

     } else if (sc.state == SCE_VHDL_BLOCKCOMMENT) {
       if (sc.Match('*', '/')) {
         sc.Forward();
         sc.ForwardSetState(SCE_VHDL_DEFAULT);
       }

just before the line with if (sc.state == SCE_VHDL_STRING)
and:

       } else if (sc.Match('/', '*')) {
         sc.SetState(SCE_VHDL_BLOCKCOMMENT);

Now using TDM version of MinGW GCC

   The most recent version of GCC for Windows easily installable from
the main MinGW site is 3.x. The Linux world has moved on considerably
with 4.4 common on current distributions. TDM provide downloads of GCC
4.4.1 for Windows from http://www.tdragon.net/recentgcc/ .

   This version works well now with Scintilla and SciTE although it
required some changes in the win32 platform code. The changes needed
are in CVS. In the future, this is the version of GCC on Windows that
I will use for testing, specifically the SJLJ Unwinding version. The
versions of GCC used on Windows and Linux will be closer so there is
less chance of incompatibilities.

   To prevent a spurious warning (and it really is spurious), the
-Wno-strict-overflow flag (no warnings for strict overflow compliance)
is used with GCC on both Windows and Linux.

   Neil

--

-- 
You received this message because you are subscribed to the Google Groups "scintilla-interest" group.
To post to this group, send email to scintilla-interest <at> googlegroups.com.
To unsubscribe from this group, send email to scintilla-interest+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/scintilla-interest?hl=en.

Re: VHDL Block Comment /* */ support in SciLexerVHDL

Hi Philippe,
Thank you for your prompt reply. Appreciate your help, I will try it
out.

On Mar 3, 9:48 pm, Philippe Lhoste <Phi... <at> GMX.net> wrote:
> On 03/03/2010 02:19, chanhuai wrote:
>
> > I can compile the file and integrate it to my environment if there's a
> > patch.
>
> OK, here is a quick hack.
> In SciLexer.h, you have to add the line:
>
> #define SCE_VHDL_BLOCKCOMMENT 15
>
> preferably after the SCE_VHDL_USERWORD definition.
> Of course, in your vhdl.properties file, you add:
>
> # Block comments
> style.vhdl.15=$(colour.code.comment.box),$(font.code.comment.box)
>
> or something similar (your choice of style).
>
> Now, just add the lines:
>
>      } else if (sc.state == SCE_VHDL_BLOCKCOMMENT) {
>        if (sc.Match('*', '/')) {
>          sc.Forward();
>          sc.ForwardSetState(SCE_VHDL_DEFAULT);
>        }

rectangular selection, un-indenting fix

Re: rectangular selection, un-indenting fix

 Todd Whiteman:

> This is a 1-line patch to allow Shift+Tab to unindent a rectangular
> selection, becoming similar to what Tab does to indent the selection.

    OK, committed.

    Neil

--

-- 
You received this message because you are subscribed to the Google Groups "scintilla-interest" group.
To post to this group, send email to scintilla-interest <at> googlegroups.com.
To unsubscribe from this group, send email to scintilla-interest+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/scintilla-interest?hl=en.

How to use Scintilla framework in Cocoa project?

Hi,

Sorry to ask such a n00b question, but searching the web and having
made lots of attempts at this hasn't worked for me so far.

I'd like to use Scintilla in a Cocoa project. I'm new to Cocoa and
Objective-C, but it looks like using the Scintilla framework, as
included in the source, ought to be simple. However, I can't get my
application to compile - one way or another it complains either about
Selection.h being missing or, if I include all of the Scintilla source
in my project, about the redeclaration of class Point.

I've looked at how ScintillaTest includes ScintillaFramework, but
can't learn anything from that - doing something similar in my own
project complains about missing headers. I'd assumed that
ScintillaTest is a demo of how to use ScintillaFramework, and that to
use Scintilla in my own project I don't need to include files from
ScintillaTest; that is right isn't it?

I realise that this is probably something pretty simple, but it has me
stumped. Any kind soul care to point me in the right direction please?

Cheers,
R

--

-- 
You received this message because you are subscribed to the Google Groups "scintilla-interest" group.
To post to this group, send email to scintilla-interest <at> googlegroups.com.
To unsubscribe from this group, send email to scintilla-interest+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/scintilla-interest?hl=en.

Re: How to use Scintilla framework in Cocoa project?

Richard J. Turner:

> I'd like to use Scintilla in a Cocoa project. I'm new to Cocoa and
> Objective-C, but it looks like using the Scintilla framework, as
> included in the source, ought to be simple. However, I can't get my
> application to compile - one way or another it complains either about
> Selection.h being missing or, if I include all of the Scintilla source
> in my project, about the redeclaration of class Point.

   You need to turn on namespaces so that Scintilla's Point does not
clash with the platform's Point. In a makefile add -DSCI_NAMESPACE.
For Xcode, in the Get Info boxes for the target, select the Build tab
and set the GCC 4.0 Preprocessing | Preprocessor Macros setting to be
SCI_NAMESPACE SCI_LEXER.

> I've looked at how ScintillaTest includes ScintillaFramework, but
> can't learn anything from that - doing something similar in my own
> project complains about missing headers. I'd assumed that
> ScintillaTest is a demo of how to use ScintillaFramework, and that to
> use Scintilla in my own project I don't need to include files from
> ScintillaTest; that is right isn't it?

   I haven't looked at it for a while. I think ScintillaTest is meant
more for testing than as an example.

   Neil

--

-- 
You received this message because you are subscribed to the Google Groups "scintilla-interest" group.
To post to this group, send email to scintilla-interest <at> googlegroups.com.
To unsubscribe from this group, send email to scintilla-interest+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/scintilla-interest?hl=en.