Re: [Oorexx-devel] Multi-line literals

2016-11-02 Thread Mike Cowlishaw
> As long as we're going "extra-ANSI", wouldn't the square > brackets [ ... ] be more indicative of a "block" of data? Or > are they already being used and I missed it? Already used. For example, pretty much all my memowiki page Rexes start: use arg data., source, html, kind signal on

Re: [Oorexx-devel] Multi-line literals

2016-11-02 Thread Mike Cowlishaw
I've had this idea in the back of my head for a literal that could be converted into an object of a particular type, for example, XML, Using a second trigger character like that would allow the type to be specified. For example, specs = {/XML' ...

Re: [Oorexx-devel] Multi-line literals

2016-11-02 Thread Chip Davis
As long as we're going "extra-ANSI", wouldn't the square brackets [ ... ] be more indicative of a "block" of data? Or are they already being used and I missed it? -Chip- On 11/2/2016 9:48 AM, Mike Cowlishaw wrote: >> +1 > > Equally to 'blow' the use of {} for just one rarely-needed syntax

Re: [Oorexx-devel] Multi-line literals

2016-11-02 Thread Rick McGuire
I've had this idea in the back of my head for a literal that could be converted into an object of a particular type, for example, XML, Using a second trigger character like that would allow the type to be specified. For example, specs = {/XML' ... wrote: > > +1 > > Equally to 'blow' the use

Re: [Oorexx-devel] Multi-line literals

2016-11-02 Thread René Jansen
come to think of it, I think it would be better if the delimiter cannot be on the same line. JCL has: //DD1 DD *,DLM=AA . . data . AA which always suited me fine. Just paste a block in there. Python has “here documents” which look … similar: COMMAND < On 2 nov.

Re: [Oorexx-devel] Multi-line literals

2016-11-02 Thread Mike Cowlishaw
> +1 Equally to 'blow' the use of {} for just one rarely-needed syntax would be a profligate waste :-). So, reserving a character inside for specific purposes would make sense (and make the notation more obvious -- we know all too well that in some fonts, etc., it's hard to tell '{' from '(',

Re: [Oorexx-devel] Multi-line literals

2016-11-02 Thread René Jansen
+1 > On 31 okt. 2016, at 20:48, Rick McGuire wrote: > > Well, there's always { and }, which never gets used because we're constantly > saving them for something in the future. > > Rick > --

Re: [Oorexx-devel] Multi-line literals

2016-11-01 Thread Rony G. Flatscher
On 31.10.2016 20:48, Rick McGuire wrote: > Well, there's always { and }, which never gets used because we're constantly > saving them for > something in the future. > > Rick +1 > On Mon, Oct 31, 2016 at 3:16 PM, Mike Cowlishaw > > wrote: > >

Re: [Oorexx-devel] Multi-line literals

2016-10-31 Thread Rick McGuire
Well, there's always { and }, which never gets used because we're constantly saving them for something in the future. Rick On Mon, Oct 31, 2016 at 3:16 PM, Mike Cowlishaw wrote: > > > > Using /' ... '/ or /" ... "/ for multiline literals >> > > This is not an option, as

Re: [Oorexx-devel] Multi-line literals

2016-10-31 Thread Mike Cowlishaw
Using /' ... '/ or /" ... "/ for multiline literals This is not an option, as e. g. say 2 /" 3 "/ 4 is already a valid expression Indeed; I was definitely not suggesting a specific syntax, just trying to indicate the concept. Mike

Re: [Oorexx-devel] Multi-line literals

2016-10-31 Thread Erich Steinböck
> > Using /' ... '/ or /" ... "/ for multiline literals > This is not an option, as e. g. say 2 /" 3 "/ 4 is already a valid expression -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi

Re: [Oorexx-devel] Multi-line literals

2016-10-31 Thread Rony G. Flatscher
post_title', 'post_excerpt', 'post_status', 'comment_status','ping_status', 'post_password', 'post_name', 'to_ping','pinged', 'post_modified', 'post_modified_gmt','post_content_filtered','post_parent', 'guid','menu_order','post_type', 'post_mime_type', 'comment_count' )VALUES('"/gp.ID.1/"', '&quo

Re: [Oorexx-devel] Multi-line literals

2016-10-19 Thread Mike Cowlishaw
9 October 2016 13:54 To: oorexx-devel@lists.sourceforge.net Subject: Re: [Oorexx-devel] Multi-line literals On 19.10.2016 11:37, René Jansen wrote: I beg to differ here. Now it means that every ‘sublanguage’ fragment needs to be embedded in quotes, checked on quotes in comments or embedded quotes of th

Re: [Oorexx-devel] Multi-line literals

2016-10-19 Thread Rony G. Flatscher
----------- >>> *From:* Rick McGuire [mailto:object.r...@gmail.com] >>> *Sent:* 14 October 2016 22:04 >>> *To:* Open Object Rexx Developer Mailing List >>> *Subject:* Re: [Oorexx-devel] Multi-line literals >&

Re: [Oorexx-devel] Multi-line literals

2016-10-19 Thread René Jansen
int the line where it occurred. > > Mike > >> From: Rick McGuire [mailto:object.r...@gmail.com] >> Sent: 14 October 2016 22:04 >> To: Open Object Rexx Developer Mailing List >> Subject: Re: [Oorexx-devel] Multi-line literals >> >> They were removed f

Re: [Oorexx-devel] Multi-line literals

2016-10-15 Thread Mike Cowlishaw
: [Oorexx-devel] Multi-line literals They were removed from the language because in practice, they resulted in lots of problems when a closing delimiter was accidentally omitted. It was pretty easy for a missing quote to swallow up large sections of the program without error. I'm not particularly

Re: [Oorexx-devel] Multi-line literals

2016-10-14 Thread Rick McGuire
They were removed from the language because in practice, they resulted in lots of problems when a closing delimiter was accidentally omitted. It was pretty easy for a missing quote to swallow up large sections of the program without error. I'm not particularly in favor of adding this. Rick On

[Oorexx-devel] Multi-line literals

2016-10-14 Thread Erich Steinböck
I had a look at the REX folder which mfc has provided at http://speleotrove.com/rexxhist/rexcard-208-scan.pdf and saw that we had multi-line strings already back in 1980. So I'd like to reopen the discussion about adding multi-line literals. (This is not imbedded data - now available through the