My concern with getting this done is the support for *ix systems. I
need to figure out the correct mechanism to do the redirection and write
the corresponding code. Then there is the issue of getting a *ix build
and testing that build in a *ix environment, neither of which can I do
at the moment.
As to postponing the persistent state portion, I guess I can live with
that but having it from the start will make documentation of the
functionality cleaner. (If it's not there initially, we need to clearly
state that fact and then remove the restriction later when it gets added.)
Gil
PS The ANSI standard does define error messages in the BNF description
which might also help with doing the parsing. There is a link
(http://www.rexxla.org/rexxlang/standards/j18pub.pdf) to the approved
final draft and page 35 has the BNF for the ADDRESS keyword. FWIW GB
On 3/30/2018 12:42 PM, Rick McGuire wrote:
Hmmm, I'm very much of the opposite opinion. I could have something
working in a week or two. I've got a fair amount of the code written
already, although I'm now at the tedious part of doing the command
parsing and getting all of the error messages defined. The only part
I'm really missing is the handling of the redirection of the actual
command.
I do want to note that currently, I am only implementing the version
of this that uses full command invocation, i.e.,
ADDRESS env command WITH INPUT STEM a.
But not the version where you set a persistent invocation state for an
environment
ADDRESS env WITH INPUT STEM a.
There are some aspects of that I don't like, so I'm going to have to
think that one over a bit. It might still be doable, but I'm not
committing to it. The full command version is the part everybody
wants, so we can always roll out the fuller support later if there is
demand.
Rick
On Fri, Mar 30, 2018 at 11:51 AM, Gil Barmwater
<[email protected] <mailto:[email protected]>> wrote:
While I, too, am excited about ADDRESS WITH and am sure we will
move much more quickly with Rick's involvement than if I were
tackling it alone, I cannot estimate how long this will take to
complete. So, my recommendation is to NOT hold the release of
5.0.0 for any longer than necessary to resolve the other issues
that have already been identified. We can do a 5.1.0 when ADDRESS
WITH is ready and/or the RXAPI issues are resolved. FWIW.
Gil
On 3/30/2018 11:02 AM, René Jansen wrote:
Moritz,
After Gil’s talk I am also excited about ADDRESS WITH (and the
fact that it has been taken up by Rick) so we might hold off
the freeze for some time until we have all infrastructure and
installers ready (and maybe have ADDRESS WITH). Maybe this
gives us also time to look into the portable version again. I
personally think this would be a great boost for takeup.
I remember you had a set of patches to turn the sockets of
rxapi into pipes. I do not remember if this was windows-only
or also included linux/macos.
The issues with rxapi:
- you must be authorized to run it on its port
- the firewall must allow access (cost me great headaches on
Z, where the standard image for a Linux VM was very
restrictive, and you got a timeout and no message)
- you must be authorized to start it, so that means a service
on windows or some systemd / startup item
- it writes a PID file so whoever starts it, must be
authorized to write there
Thing is, solutions must work for the three main platforms,
that is the reason of my question.
best regards,
René
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
<https://lists.sourceforge.net/lists/listinfo/oorexx-devel>
--
Gil Barmwater
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
<https://lists.sourceforge.net/lists/listinfo/oorexx-devel>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
--
Gil Barmwater
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
