Re: 9.0.1 token colours

Found another oddity -- in the following snippet, the "on-error" is lit up
like "Operation", but "monitor" and "endmon" seem to be "Free-form
Control-flow Opcode". Looks odd with one standing out like that.


/free

monitor;
dosomething( withThis );
on-error;
tellsomeone( this );
endmon;

/end-free


Also, I have to agree with Buck -- it's quite a mess, and I too am mainly
interested in comments, opcodes and garbage (indicators).
I can't imagine anyone editing with every category a different color (i.e.
the way it was shipped) -- might bring on seizures!

So for now, spec is light purple (so I can ignore them), comments are a
light pink (so I can ignore them), "Macro Keyword" orange, everything else
is black.

Stu







On Mon, Dec 16, 2013 at 2:40 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

<created a new thread>

Edmund said:

That is an interesting response. We were getting complaints
about the previous tokenizer not distinguishing between tokens,
so we added this as an enhancement.

I would like to hear what others thing about style
directives. Should we make distinctions between tokens or not.

I'm probably going to be the controversial one in this thread. I've
never cared for the choices I have with the token colours. For those
following along, open the colour picker up: Preferences > LPEX Editor >
Parsers > Parser styles.

I agree with Vern: the nomenclature for the RPG tokeniser doesn't match
what RPG programmers think about tokens. Click on 'User Symbol' and
then click the check box to the right labelled 'Outline'. Now you can
see what 'User Symbol' refers to. F-spec file name, D-spec variable
name, I-spec file name, I-spec field name, C-spec factor 2, O-spec
EXCEPT name, O-spec field name, O-spec constant, P-spec procedure name,
D-spec procedure name. There may be more, because the Preview box
doesn't have the full suite of RPG specs - for example, there are no
extended factor 2 EVAL statements, and 'Macro Statement' is
unrepresented. Anyway, as an RPG programmer, there's no possible way I
would ever think of factor 2 the same as a file name the same as an
O-spec constant. That token - 'User Symbol' - is way overloaded to be
useful to me. So I changed it to black.

Unclick Outline and click User Symbol2, then click Outline again. This
one is factor 1 and the result field. Not nearly as overloaded as User
Symbol, but as an RPG guy I'd way rather know when things are getting
changed - result field - than overloading result with factor 1. Changed
colour to black.

Keyword. Holy cow. When I click Outline, it seems like half the
Preview has boxes. Changed colour to black.

What is the difference between Numeric and Numeric2, and why aren't
array indices [ARRAY(1)] considered numeric but F-spec record lengths
are? Black and black.

The compile time arrays are interesting. The first 5 characters are
colourised as 'Comment' and the remaining characters are 'Data'. Since
I like my comments to stand out, I'm forced to change 'Data' to match.
I make mine a sort of purple. Do those colours have names?

In the end, the only colours I have are indicators (I want the weeds to
stand out), BIFs, opcodes and comments. The reason I'm writing is
because Edmund asked, and I thought the team should know how one (very
old, ahem I mean experienced) user treats these colour choices.
Clearly, they aren't that important to me, but I definitely respect the
opinion of those who differ. As long as I can set them to black, I'm
happy :-)

--buck

Stu said:
Got it installed. Lots of new "syntax coloring" options.

I think one is miscategorized, though, leading to ugliness:

In this directive

/include srcfile,srcmbr

or this one

/if defined(condition)

the bit after the "keyword" (the file,mbr for example, or
(condition) ) used to be categorized as "Macro Statement"
but is now "Free-form Identifier". First off, it's not
an identifier, and second it mixes these in with actual
"Free-form Identifiers" (like file, variable and procedure
names) and ends up looking sloppy. I used to be able to
have all the macros in one color, now I cannot.

--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.