I'm inclined to err on the side of caution, myself. After all, this is introducing a new keyword for the ADDRESS statement with a potential for breakage; e.g.

  with = 'C:\Chip\bin\'
  Address COMMAND 'DIR' with

At the very least, that will generate an astonishing error message ("Error 25: Invalid sub-keyword found" on Regina) in previously working code. I don't think we should spring that on the community without a fair amount of warning.

We'll need  to update the existing test units for 'Address' and the docs.

Rick may have something ready in a week but I'm inclined to treat it as a prototype until we have all our other ducks in a row. We have experience with, and thus a fairly high level of confidence in the current 5.0.0 release candidate. Let's get it out unchanged and use it's announcement to draw attention to the long-awaited 'Address-With' feature, "coming soon".

ooRexx 4.2.0 has been out for four (!) years. Let us not delay 5.0.0 any longer.

-Chip-

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



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

Reply via email to