On Wed, Sep 24, 2014 at 4:49 PM, Sahananda (Jon) Wolfers <
sahana...@windhorse.biz> wrote:
> Looks good, a few questions though:
>
> Does it always have to be line based?
>
Yes it does...at the point where parsing occurs, the program has already
been broken up into a collection of lines. Worryin
Looks good, a few questions though:
Does it always have to be line based?
Are characters that are not permitted in a rexx program normally allowed
here?
If the Terminator has to be at the start of a line, is the final line-end
character(s) part of the resource?
thanks,
Jon
On 24 September 2014
I have an initial stab at implementing this now. I decide on ::RESOURCE for
the directive name. Here's a short sample of how it works now:
loop name over .resources~names
say name
end
loop name over .resources~namesToo
say name
end
::resource names
Rick
Mike
::END
::resource namesToo end
Rick, I like the idea of including a "Data" directive of this sort.
Ok, if I understand correctly, the suggestion is to be able to define
some data in the program with the syntax of
::Data data1
::enddata
::Data data2
::enddata
The examples above define two different "groups" of data, one cal
Still not getting what point you are trying to make. That is exactly what
I'm showing. The data is retrieved from the program package by the name
shown in the directive.
mydata = .context~package~data('Data1')
or
mydata = .context~package~data('Data2')
you can have as many data sections in th
You might want to look in the incubator at the texttemplate entry. There
is some code I wrote there to do text substitution on text files that
might be of use to the ::Data effort.
David Ashley
--
HPCC Systems Open Sourc
But what if a program needs to include two ::DATA directives in a single
package? In this case we would need to determine which one we wanted to
work with.
David Ashley
On Mon, 2014-06-16 at 11:09 -0400, Rick McGuire wrote:
> Not sure what you mean...::Data directives are paired with an end
> mar
Not sure what you mean...::Data directives are paired with an end marker,
so
::Data data1
::enddata
::Data data2
::enddata
Is perfectly well defined syntax. The end marker does not need to be
uniquely defined for every directive and in generally, the end marker only
needs to be redefined if th
We also need a way to determine which ::Data directive we are working
with should there be multiple directives in the package.
David Ashley
--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Fin
On Mon, Jun 16, 2014 at 9:33 AM, David Ashley
wrote:
> Sorry, I was out of pocket most of the weekend so I did not see this
> until today.
>
> I have also wanted/requested this feature for some time. It seems only
> natural that in an object oriented language that data and program be
> held toget
Sorry, I was out of pocket most of the weekend so I did not see this
until today.
I have also wanted/requested this feature for some time. It seems only
natural that in an object oriented language that data and program be
held together in a single entity (an ooRexx program or class file).
One sug
On Sat, Jun 14, 2014 at 1:26 PM, Mike Cowlishaw wrote:
>
>
>
> This is similar to MIME encoding, but ooRexx already has the directive
> concept that breaks the code into units. That is the link into the address
> space/naming mechanism. I have toyed with also adding Mime sort of typing
> mecha
This is similar to MIME encoding, but ooRexx already has the directive concept
that breaks the code into units. That is the link into the address space/naming
mechanism. I have toyed with also adding Mime sort of typing mechanisms to
this, but I think I'd prefer to keep this simple right now,
btw, I've gone ahead and created a feature request for multi-line literals:
https://sourceforge.net/p/oorexx/feature-requests/597/
On Sat, Jun 14, 2014 at 12:18 PM, René Jansen wrote:
> I am in favor of a https://en.wikipedia.org/wiki/Here_document perl, ruby
> style of doing this.
> If it can
This is similar to MIME encoding, but ooRexx already has the directive
concept that breaks the code into units. That is the link into the address
space/naming mechanism. I have toyed with also adding Mime sort of typing
mechanisms to this, but I think I'd prefer to keep this simple right now,
but
This is something I've been thinking about for some time, and we even have a
couple of RFEs open for something like this (though in fairness, I opened one of
these). On occasion, I find I'd like to write a program that needs some
associated data. Coding the data as a series of assignment state
I do for see a use for multi-literals, but I don't really see them as being
a good usage for the type of problem I'm trying to solve here. The
directive approach is really intended for situations where I really wish to
embed a file within a single source program rather than having it
elsewhere. I
I am in favor of a https://en.wikipedia.org/wiki/Here_document perl, ruby style
of doing this.
If it can be can simple syntax, and not require directives, it can be
compatible with a NetRexx implementation.
René.
On 14 jun. 2014, at 15:42, Rick McGuire wrote:
> This is something I've been t
This sounds pretty good.
I confess it is not something that I have desired, but I can think of uses
for it if it was available.
--
Mark Miesfeld
On Sat, Jun 14, 2014 at 6:42 AM, Rick McGuire wrote:
> This is something I've been thinking about for some time, and we even have
> a couple of RFE
I, too, have seen a need for something like this for quite a while. And
I've written some functions using sourceline to accomplish it but they
preclude the use of REXXC as you've noted. So I'd like to see an
"official" solution get agreed on and implemented.
I would like to distinguish, howev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I think this is a good idea, but I'm not convinced adding another
directive is the right way to go. Directives do not integrate well with
the flow of programs as they are static in a way. Adding those data
directives could be imagined as having s
This is something I've been thinking about for some time, and we even have
a couple of RFEs open for something like this (though in fairness, I opened
one of these). On occasion, I find I'd like to write a program that needs
some associated data. Coding the data as a series of assignment statemen
22 matches
Mail list logo
