Proposed ENHANCEMENT to the PARSE statement
Locked
 
|
What did orry be most, with the PARSE statement, which is excellent, by
the way, is as follows: PARSE doesn't honour QUOTES (") and APOSTROPHES('), *when they are the *Leading character*, only, I would propose, in a pattern to be parsed to surround a single Literal, obtained as a *single tem* in a PARSE statement. This (new) feature would be very valuable, of course, as it would allow, for instance, the direct use of PARSE, when parsing a DB2 LOAD file, for instance, which does require all Textsto be surrounded by double quotes, as you all now, for sure. There are so many other software packages who use this convention, as well. Might well be that we shouldd *only* allow DOUBLE QUOTES ('), for this piurpose, but that should be discussed, of course, This convention might be also valuable for ALL Rexx Dialects, but I've been asked too many times to *not double post* both to RexxLA and ibm-netrexx, I'm raising this discussion here only. By the way, as far as I do know, all important Rexx Developers and maintainers are on this list, as well. Please let discuss us this proposal *unanimously*, when possible at all (Chip will of course say: Thomas always wants to change the language ... ;-) YES, I *do want* to make it even more human! Kind regards from Vienna, Austria, *and* a happy and relaying weekend for you all ! :-) Thomas Schneider. -- Thomas Schneider CEO ThSITC IT Consulting KG Erdbergstr. 52-60/1/13 1030 Wien Austria, Europe Skype ID: Thomas.Schneider.Wien Member of the Rexx Languge Asscociation (www.rexxla.org) Member of the NetRexx Developer's Team (www.netrexx.org) _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/
Thomas Schneider, Vienna, Austria (Europe) :-)
www.thsitc.com www.db-123.com |
Re: Proposed ENHANCEMENT to the PARSE statement
|
Please provide an example so that I (and others) could understand what you wish to achieve.
Walter _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
In reply to this post by ThSITC
Thomas,
if every element of the source has quotes around it, I translate the quotes to spaces and then parse around the separators. Is this what you mean? best regards, René. On 2012-08-03 12:16, Thomas Schneider wrote: > What did orry be most, with the PARSE statement, which is excellent, > by the way, is as follows: > > PARSE doesn't honour QUOTES (") and APOSTROPHES('), *when they are > the *Leading character*, only, I would propose, > in a pattern to be parsed to surround a single Literal, obtained as a > *single tem* in a PARSE statement. > > This (new) feature would be very valuable, of course, as it would > allow, for instance, the direct use of PARSE, > when parsing a DB2 LOAD file, for instance, which does require all > Textsto be surrounded by double quotes, as > you all now, for sure. > > There are so many other software packages who use this convention, as > well. > > Might well be that we shouldd *only* allow DOUBLE QUOTES ('), for > this piurpose, but that should be discussed, of course, > > This convention might be also valuable for ALL Rexx Dialects, but > I've been asked too many times to *not double post* > both to RexxLA and ibm-netrexx, I'm raising this discussion here > only. > > By the way, as far as I do know, all important Rexx Developers and > maintainers are on this list, as well. > > Please let discuss us this proposal *unanimously*, when possible at > all (Chip will of course say: Thomas always wants to > change the language ... ;-) > > YES, I *do want* to make it even more human! > > Kind regards from Vienna, Austria, > > *and* > > a happy and relaying weekend for you all ! :-) > > Thomas Schneider. _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
In reply to this post by christel.u.w.pachl christel.u.w.pachl
And, assuming that it's not easily accomplished by existing Rexx
features, how you propose to implement it in a manner that does not break existing programs. -Chip- On 8/3/2012 11:37 Walter Pachl said: > Please provide an example so that I (and others) could understand what you wish to achieve. _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
As always, Chip!
probably a NEW OPTION ??? ... to maintain upwards compatibility, which is SO important! ...... but has been NEVER honoured by the family of Rexx Languages: a) classic Rexx b) ANSII Rexx c) Object Rexx (NOT upwards compatible to ANSII Rexx) d) NetRexx Hence, as a matter of fact, we do now have 4 Languages, at least! It's becoming more and more difficult to remind the differences! Massa Thomas ;-) ================================================================ Am 03.08.2012 21:56, schrieb Chip Davis: > And, assuming that it's not easily accomplished by existing Rexx > features, how you propose to implement it in a manner that does not > break existing programs. > > -Chip- > > On 8/3/2012 11:37 Walter Pachl said: >> Please provide an example so that I (and others) could understand >> what you wish to achieve. > > _______________________________________________ > Ibm-netrexx mailing list > [hidden email] > Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ > > -- Thomas Schneider CEO ThSITC IT Consulting KG Erdbergstr. 52-60/1/13 1030 Wien Austria, Europe Skype ID: Thomas.Schneider.Wien Member of the Rexx Languge Asscociation (www.rexxla.org) Member of the NetRexx Developer's Team (www.netrexx.org) _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/
Thomas Schneider, Vienna, Austria (Europe) :-)
www.thsitc.com www.db-123.com |
Re: Proposed ENHANCEMENT to the PARSE statement
|
|
Thomas,
It seems to me you that are railing against the inevitable. Each of these follow-ons to Rexx has been created because it contained concepts that could not be reconciled with its predecessors, hence the only option was a clean break. Of course there is no compatibility between the four. Even if it were possible to create an "uber Rexx" that did it all, it would surely be an appalling mess. The "Rexx family of languages" is a myth: all they share is some convenient syntax. It is like calling C, C++ and Java the "C family of languages" because they all use C-like syntax. [A symposium was held some years ago on this "family" with their three inventors as a panel. Each vociferously denied that their language bore any significant resemblance to the others.] Re the parsing proposal, surely you agree with Chip: would you want to wake up tomorrow to discover that some of your NetRexx programs had stopped working because of an incautious language "improvement"? Anything done without careful consideration is a menace. Fortunately, the machinery is in place to prevent this. I deal with the issue of "reminding the differences" by focusing my attention solely on NetRexx. On Fri, Aug 3, 2012 at 6:31 PM, Thomas Schneider <[hidden email]> wrote: As always, Chip! -- "One can live magnificently in this world if one knows how to work and how to love." -- Leo Tolstoy _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
«
Return to ibm-netrexx
|
1 view|%1 views
| Free forum by Nabble | Edit this page |