colour highlighting of syntax

Sorry if this is misplaced, I've had a look through stickies and FAQs but can't find out how to post code that is syntax highlighted in colour.

I assume there is a utility that understands C and C++ syntax and also vBulletin colour tags but is it standalone or an editor plug-in?

I'm using TextPad on Windows XP and vi on Suse Linux and Ubuntu Linux and vim on Cygwin. These have their own colour syntax highlighting but do not use vBulletin [COLOR] tags.

I've written a painter. It is in my signature.

Quote:

---

Originally Posted by siavoshkc

I've written a painter. It is in my signature.

---

Got it. Thx v much. You're a star.

Code:

---

#include <stdio.h>

int main(void) {
    int ch;

    while ((ch = getchar()) != EOF)
        if (ch == '\n')
            printf("\n");
        else
            printf("%0x ", ch ^ 0xaa);

    return 0;
}

---

There are three code colourers written by members of this board as far as I'm aware. siavoshkc's "code painter", Code Colorer v2.0 by Martin, and my codeform. (codeform's somewhat old and I'm rewriting it right now.)

Here's a recent thread where we argue about which is the best: http://cboard.cprogramming.com/showthread.php?t=82592

Quote:

---

Originally Posted by dwks

There are three code colourers written by members of this board

---

Yes, thanks. I tried them all:

CPP code tagger

Code:

---

#include <stdio.h>

int main(void) {
    int ch;

    while ((ch = getchar()) != EOF)
        if (ch == '\n')
            printf("\n");
        else
            printf("%0x ", ch ^ 0xaa);

    return 0;
}

---

Color Coder V 2.0

Code:

---

#include <stdio.h>

int main(void) {
    int ch;

    while ((ch = getchar()) != EOF)
        if (ch == '\n')
            printf("\n");
        else
            printf("%0x ", ch ^ 0xaa);

    return 0;
}

---

codeform

Code:

---

#include <stdio.h>

int main(void) {
    int ch;

    while ((ch = getchar()) != EOF)
        if (ch == '\n')
            printf("\n");
        else
            printf("%0x ", ch ^ 0xaa);

    return 0;
}

---

And I do believe that codeform does have that little something extra; plus, with a little adjustment, I can use it on my Linux systems. Thanks dwks.

Adjustment:
- I removed the forward slash from the definition of the default dat file as forward slash is the Windows-specific directory path separator

Note:
- Neither Linux nor Windows liked the numbercol definition in codeform_cb_cpp.dat (the equal symbol before darkblue needs a backslash escape character)

[numbercol]
\[color=darkblue]=[/color]

It says

Quote:

---

Originally Posted by codeform

Syntax error in data file "codeform.dat" on line 112:
[numbercol]'s data must have 2 parts (it has 3)

---

I've got my own, but it gets color happy if you use keywords in parts of your variable names... for example, int sprint would look bad.

Code:

---

#include <stdio.h>

int main(void) {
    int ch;

    while ((ch = getchar()) != EOF)
        if (ch == '\n')
            printf("\n");
        else
            printf("%0x ", ch ^ 0xaa);

    return 0;
}

---

oh yeah, and it's C++ specific... or I should say C wasn't included in it's design considerations as you can see from the code above.

try some harder cases... like

printf("while Fooo if bar \"stuff\" foo break 'bar'....");

I can tell you before I do it that those escapes wil break my coloring:

Code:

---

printf("while Fooo if bar \"stuff\" foo break 'bar'....");

---

yep :)

Quote:

---

Originally Posted by major_small

I've got my own, but it gets color happy if you use keywords in parts of your variable names... for example, int sprint would look bad.

Code:

---

            printf("%0x ", ch ^ 0xaa);

---

oh yeah, and it's C++ specific... or I should say C wasn't included in it's design considerations as you can see from the code above.

---

It seems that the consideration that keywords should be delimited by whitespace was also not in the design.

Have you ever thought of fixing it or would that be a completely bizarre suggestion on my part?

Quote:

---

Originally Posted by risby

It seems that the consideration that keywords should be delimited by whitespace was also not in the design.

---

I have thought of that, and at first glance it seems like a good idea... but that won't always work: static_cast<int>(12.5);

I think you'll have to introduce somehow the notion of delimiters into your keyword implementation and parse with these in mind as left-hand side delimiters.

Delimiters will be BOF, newline, whitespace, comma, semi-colon, (, {, <... if nothing is escaping me.

Any keyword may only be preceded by those above. Anything other than that will have another meaning.

EDIT: actually the above will not work for situations like int introduce. So, there also needs to be a list of right hand side delimiters.

Quote:

---

Originally Posted by risby

It seems that the consideration that keywords should be delimited by whitespace was also not in the design.

Have you ever thought of fixing it or would that be a completely bizarre suggestion on my part?

---

More correctly they should be delimited by word boundaries, i.e. /\b\w+?\b/.

I just use Vim's Convert to HTML and filter that through a Perl script to get BBCode whenever I want to get pretty. E.g.

Code:

---

1 #include <stdio.h>
2
3 int main(void) {
4     int ch;
5
6     while ((ch = getchar()) != EOF)
7         if (ch == '\n')
8             printf("\n");
9         else
10             printf("%0x ", ch ^ 0xaa);
11     printf("while Fooo if bar \"stuff\" foo break 'bar'....");
12
13     return 0;
14 }
15

---

Anyway my code painter handle it easily.

Code:

---

printf("while Fooo if bar \"stuff\" foo break 'bar'....");

---

Quote:

---

Originally Posted by Perspective

try some harder cases... like

printf("while Fooo if bar \"stuff\" foo break 'bar'....");

---

None of them failed the Perspective test:

SiavoshKC's

Code:

---

#include <stdio.h>

int main(void) {
    int ch;

    while ((ch = getchar()) != EOF)
        if (ch == '\n')
            printf("\n");
        else
            printf("%0x ", ch ^ 0xaa);
    printf("while Fooo if bar \"stuff\" foo break 'bar'....");

    return 0;
}

---

Martin's

Code:

---

#include <stdio.h>

int main(void) {
    int ch;

    while ((ch = getchar()) != EOF)
        if (ch == '\n')
            printf("\n");
        else
            printf("%0x ", ch ^ 0xaa);
    printf("while Fooo if bar \"stuff\" foo break 'bar'....");

    return 0;
}

---

dwks'

Code:

---

#include <stdio.h>

int main(void) {
    int ch;

    while ((ch = getchar()) != EOF)
        if (ch == '\n')
            printf("\n");
        else
            printf("%0x ", ch ^ 0xaa);
    printf("while Fooo if bar \"stuff\" foo break 'bar'....");
    return 0;
}

---

This is thanks do dwks, I think they all pass that too -

Code:

---

printf("hi");

#define /*what?*/ foo

puts("\\\"");

in\
t x;

printf("/*comment*/");

/* int x; printf("int x;"); */

// /*
for(;;){}
//*/

/*//*/ int okay;

---

Or at least they don't break upon implementation :)

Quote:

---

Note:
- Neither Linux nor Windows liked the numbercol definition in codeform_cb_cpp.dat (the equal symbol before darkblue needs a backslash escape character)

[numbercol]
\=

It says

Quote:

---

Originally Posted by codeform

Syntax error in data file "codeform.dat" on line 112:
[numbercol]'s data must have 2 parts (it has 3)

---

---

Yes, that was an error I forgot to fix before posting it.

I have a few really tricky ones for you:

Code:

---

#define x printf("") /* comment */
#define x printf("/*") /* comment */
#define x printf("//")
#define x printf(" /* " // "*/");
/* #define x x */
// /*
#define x /**/

---

I'm currently re-writing codeform. The new version is 1.2.0 and it should be ready in a week or so (maybe two).

Code:

---

#define x printf("") /* comment */
#define x printf("/*") /* comment */
#define x printf("//")
#define x printf(" /* " // "*/");
/* #define x x */
// /*
#define x /**/

---

Quote:

---

I'm currently re-writing codeform. The new version is 1.2.0 and it should be ready in a week or so (maybe two).

---

What are its features?

SiavoshKC's prog does this

Code:

---

#define x printf("") /* comment */
#define x printf("/*") /* comment */
#define x printf("//")
#define x printf(" /* " // "*/");
/* #define x x */
// /*
#define x /**/

---

and Martin's does this

Code:

---

#define x printf("") /* comment */
#define x printf([COLOR=RED]"/*") /* comment */
#define x printf("//")
#define x printf(" /* " // "*/");
/* #define x x */
[COLOR=GREEN]// /*
#define x /**/

---

and dwks' codeform

Code:

---

#define x printf("") /* comment */
#define x printf("/*") /* comment */
#define x printf("//")
#define x printf(" /* " // "*/");
/* #define x x */
// /*
#define x /**/

---

which, by my reckoning, puts SiavoshKC's CPP Code Painter in the lead at the moment.

How do you come up with these beauts dwks?

Quote:

---

Originally Posted by risby

which, by my reckoning, puts SiavoshKC's CPP Code Painter in the lead at the moment.

---

So it's still tied with Vim, then:

Code:

---

#define x printf("") /* comment */
#define x printf("/*") /* comment */
#define x printf("//")
#define x printf(" /* "// "*/");
/* #define x x */
// /*
#define x /**/

---

Except for the gaudy colors :p

How about:

Code:

---

#if !defined DOODAH
#endif

---

Most editors/ides I've used handle the '#if' but omit highlighting for the whole of #if !defined'.

It colors everything as a preprocessor directive.

Code:

---

#if defined DOODAH
#endif

---

Sorry, I meant some editors that just highlight the preprocessor directive itself would only highlight the #if and leave the '!defined DOODAH' unaffected. I note that msvc2005 can handle this but scite/wscite does not (and probably any other editor that uses the scintilla widget).

Code::Blocks highlights the whole text. It does use the scintilla widget

I'm not describing highlighting the entire line, only the preprocessor directive itself.

You can configure the scintilla widget to behave in a similar fashion with regards to highlighting preprocessor directives as msvc.

But if you do so, it will not highlight the whole of that line containing that particular preprocessor directive ie, you'll get

Code:

---

//scintilla does this if configured to highlight only the directive:
#if !defined DOODAH

---

instead of

Code:

---


#if !defined DOODAH

---

As far as I know, code::blocks doesn't yet implement this feature of the scintilla widget.

Note that when so configured the scintilla widget will highlight other preprocessor lines as expected, eg

Code:

---

#define BLAH_BLAH
#ifndef HOOHAH

---

Oh! I see your point.

My code painter will search for specific keywords in preprocessor directive line and will highlight them.

Code:

---

#if !defined CPP

---

It works now but it is not ideal.