You can’t change the color of source in CL without disturbing the source code and causing the command analyzer to throw an error.

You can change the color of comments though. You can insert display attribute hex values after the “/*” that begins a comment and before the “*/” that ends a comment. It’s possible to change colors of comments that span multiple lines by placing the hex codes at the beginning of each continued line.

Since you can embed comments with non-standard hex characters, you can create each of your non-comment statements with a leading comment that looks like “/* */” with the hex character in the middle. That causes the entire line to change, including any command on the same line. And because comments are essentially interpreted as ‘white space’, you can split your command over multiple lines and have each begin with the same distracting comment characters. (Comments can be placed between parameters of commands.)

The best advice is not to do it.

Tom

Forget about SEU ! Use the lepx editor in either WSDCi or RDi. It color codes automagically without touching the source.

Use the lepx editor…

I very much agree. I suspect, though, that we both realize that most of us learn the lesson the hard way.

Tom

oh to be able to use a modern editor, but we aren’t allowed to as that would require getting us better computers with more memory, etc. Our PCs might as well be 5250 terminals.

A Celeron, 1.8GHz, 1GB, system here runs WDSC 6 fine. A second 2.2GHz, 2GB system runs WDSC 6 & 7 fine. I run multiple other apps on both of them, nothing overwhelming. (To me, those are pretty high-end systems; but then I started serious large-scale career work back on an 8MB mainframe(!) IBM 370/168, which had dynamic address translation (virtual memory) to get us up to 12MB. I remember being impressed back then.)

I picked up an IBM “off-lease” PC at home for $160 somewhere going on a year ago to replace a PC my wife was using, and it blows this Celeron thing away.

It’s been some time since I worked for an employer who preferred paying salary over upgrading PCs once in a while. Then again, I often prefer using SEU anyway. I don’t care much for embedded colors in source though.

Tom

well, you see, salaries come out of a “different” budget.

to me it looks like left pocket or right pocket, I am still paying, but…

In all honesty, I miss the 5250-11 terminals. The best keyboard I’ve ever used; the Test mode was great for screen design; I could keep books on top of it; and I didn’t need an office heater.

salaries come out of a “different” budget.

It’s said that people rise in organizations up to their levels of incompetencies. I’d expect that to be true of those who create budgets as much as anyone else.

And remember, the CODE/400 editor still works, and it colorizes code. Not as nice as having multiple windows, but a split ring is still useful.

Tom

Actually, you can color CL code. Put the beginning color code inside comment characters – /* color */ and then your CL code. You can also do this on multiple lines to hilight longer CL commands. This also does not affect compiling the program.