Seriously, these are SAMPLES. Fiddling with this falls pretty low on my list of priorities. If the amount of effort spent obsessing over the shebang lines in the samples had been applied to building an installer, this issue would have been fixed ages ago.
Rick On Fri, Nov 16, 2018 at 10:37 AM René Jansen <[email protected]> wrote: > If we leave it in, it should be correct; because we (going forward) do not > know where the rexx executable is going to be installed (and the shebang is > one reason for that ongoing discussion), we should either use /usr/bin/env, > which will figure it out, or we need to correct the examples while > installing, which add needless complexity. I am sure that if there are > complaints, people will understand our reasoning. I think that to be able > to have one set of examples is a great good; as is the portability from > linux to windows for an exec. > > René. > > On 16 Nov 2018, at 11:29, Rick McGuire <[email protected]> wrote: > > > > On Fri, Nov 16, 2018 at 10:19 AM René Jansen <[email protected]> wrote: > >> No, it is not, in the second example the env executable looks if there is >> a rexx on the path, the first looks for a /usr/bin/env/rexx executable. >> >> My proposal: >> >> Let’s get rid of the shebang; it outlived its usefulness >> >> 1) most people I know type rexx [exec name] >> 2) on windows there is a mechanism to trigger filename suffices to an >> executable; it is not often used >> 3) most modern unix shells like bash and zsh have a mechanism to alias a >> suffix to an executable; this is what I and my friends use >> >> So in short, it is not used, it is not needed, it makes for a lot of >> discussion. >> > I disagree. There is no harm in leaving it in, and I'm not willing to deal > with all the complaints from people who expect it to be there. > > However, to address PO's specific question, it makes no sense to have a > shebang line in a .cls file in the first place since they are not intended > to be invoked as a command from the shell. The line is wrong, but > irrelevant, and should be removed. > > The latest test versions are always available from svn: > https://svn.code.sf.net/p/oorexx/code-0/test/trunk > > Rick > > > >> > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel >
_______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
