Thank you for the feedback. We will be fixing the issues regarding the use
of the word "macro", since we can understand the confusion with this. Also,
the Free-Form Identifiers style will be corrected to not include macro
statements so that they can be colored differently from identifiers.
With regards to some of the other issues or questions:
To hopefully clear up some confusion about the style of Layout Space, this
style represents that of a blank space in the source (ie: the space between
two words).
After some time trying, I do not appear to see the issue with the Data
style that Vern mentions. The double-asterisk should be considered a Data
style.
Regards,
Taryn Morris, RDi Development
---- Original Message ----
From: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>,
Date: 16/12/2013 12:06 PM
Subject: Re: [WDSCI-L] Latest fix pack
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
I found a couple other odd things - actually I don't remember visiting
the Parser Styles section before, so this is a little new to me.
First, I find the use of the word "macro" to be a bit strange - these
are called directives in the RPG reference. There is absolutely NO
mention of macros in the reference. Why the change in wording? The CPP
parser style calls #define a "CPP driective". Sigh!
Now for the example of /TITLE - this is identified as a macro. If you
put your cursor in the text that follows, it's labeled "Layout Space" -
what?
I also clicked in the example for compile time array - some of it is
labeled, in the example, as comments! The double-asterisk is labeled as
"Data".
There is almost no documentation that I've been able to find as to just
what all the style elements are - they names, as I mentioned above, do
not match anything I know from the RPG manuals. Therefore, the help is
not helpful!
Regards
Vern
On 12/16/2013 9:03 AM, Stuart Rowe wrote:
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.
Stu
midrange.com
