× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On 7/23/2013 1:14 PM, gevans@xxxxxxxxx wrote:
Using RDP 8.0.3.
I have a set of 3 lines of comments I would like to emphasize by changing
their color from "comment green" to another color, preferably red. The
code is CLLE. Can
anyone tell me if this is possible and if so, how might I go about making
this change?

The colours are done by parsing each line of code into individual
tokens. There is a separate parser for each language. The CL parser
only recognises one kind of comment, so the way it works now all the
comments would be the same colour. The only way for us to address this
would be to write our own parser and register that for the CLLE source
type. You could, for instance, make a comment /*# that would be red vs
/* that would be blue. That seems like a lot of work.

Perhaps you could share why these 3 comments in particular have more
significance than the others? There may be another solution to that
problem, and if there isn't, then perhaps one of us could make a
business case to IBM to add another 'high importance' comment type to
both the CL and ILERpg parsers by submitting an RFE.

For a kooky workaround, consider using a very long label in lieu of a
comment, and then tell the Lpex parser to colour labels red. Instead of
/* Compile this with USRPRF(*OWNER) */ you'd have
compile_this_with_usrprf_owner: The downside is that if you were to use
what looks like keywords, the tokeniser will think it's a command:
compile_this_with_usrprf(*owner): comes out in blue. As does this:
compile_this_with_usrprf_*owner: I know it's ugly. Sometimes thinking
aloud generates useful ideas.
--buck


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.