× 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.



It won't hurt, just ugly. We have the same deal going on. I just
search-and-replace the bugs with a single blank to get them out of my face.

Stu

BTW, the green-screen display attributes (x20 - x3F) are placed in unused
positions in the spec (usually column 6 for comments as the spec type for
comments is ignored by the compiler, or column 5 for active specs).




On Mon, Sep 13, 2010 at 05:21, David FOXWELL <David.FOXWELL@xxxxxxxxx>wrote:

A greenscreener is colouring his lines for SEU. I don't recall exactly how
it's done, some kind of hex code that doesn't show up on the screen? Anyway,
with WDSCi V6.1, I see a little box-shaped bug where this character must
be. It's like a little worm, eating its way into more and more code as that
developer progresses. As I am sure that RDPi or whatever it's now called
<will> eventually prevail over SEU, could this little thing be a problem one
day if left to go on like this? Like when we only have RDP and no SEU?


--
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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.