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



Hi Vern,

Can't agree more about Edmund and the team. (where do we mail the $5?)

Well, if one cannot depend on specifics in searches for specific codes, one tends to shy away from them. A search for a variable such as a single letter (in SEU or in LPEX) is daunting. One has to be creative and thoughtful in coding to make it a tad easier, such as adding a viable character like '@m' or character combos that are rare to use in normal keywords. That's been a given for RPG and other languages. And the addition of using SQL and it's available wild cards makes interesting challenges too. While it may be good to use some characters for identification, sometimes it can bite you.

I've forgotten all the work arounds for RPG that I built up over the years to assist in SEU. 20 plus years of use makes it more of instinct than remembering to avoid usages.

Duane

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Thursday, November 12, 2015 9:44 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] "M" apparently a special word in Outline

Hi Duane

Edmund and the rest of his team are going beyond the basics - the fact that they regularly participate in this list is a great benefit for us all. ($5 bill coming in the mail, Edmund!)

I want to comment on one line in your post - see it below here - I'm surprised to hear that you feel you have to modify RPG to get around things an editor forces on us.

I would think no editor should ever have behavior that prevents using what is otherwise valid code. And I am sure the RDi team feels the same way.

Of course, there might be changes in RPG - the editor might be blamed when its the language that changed out from under us. So sometimes the question might be, does the editor hang up? Or does the compile fail?
Those are errors in 2 different places.

Now the LPEX editor is a relatively young thing, compared to SEU - at about 35 years old, SEU is a gray-hair!

So I guess I can say with no fear of contradiction, to everyone, keep reporting issues, and this team will do all they can to deliver remedies.

Cheers
Vern

On 11/12/2015 8:01 AM, Duane Scott wrote:
-snip-
I've not yet learned how to modify RPG code to get around some of the restrictions that are part of using RDi.
-snip-
--
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.

________________________________
________________________________
CONFIDENTIALITY NOTICE: This electronic message transmission is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. If you have received this transmission, but are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this information is strictly prohibited. If you have received this e-mail in error, please contact NALC Health Benefit Plan at 703-729-4677 and delete and destroy the original message and all copies.





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.