Hi Mark,
thank you very much for your very interesting hint. Went back and
re-read your posting from September 30th, and indeed, it is very
possible, if not likely that in this particular case that is the reason
for the failures/errors.
All tests in the BSF4Rexx testsuite run without errors (the
On Tue, Oct 13, 2009 at 8:03 AM, Rony G. Flatscher
wrote:
> (stting in a workshop) today I have been able to not only create a
> 64-bit deb package, but also a 32-bit deb package for ooRexx from trunk,
> rev. 5257.
>
> These versions are used to run the BSF4Rexx testsuite (as for the heavy
> mult
Hi there,
(stting in a workshop) today I have been able to not only create a
64-bit deb package, but also a 32-bit deb package for ooRexx from trunk,
rev. 5257.
These versions are used to run the BSF4Rexx testsuite (as for the heavy
multithreading tests some post-release bugifxes in ooRexx are ne
I like short +1 for me too.
I did lookup .RXJ and .RXJO on filext.com, and no one else is using
those extensions, unlike .REX and .RX
Bruce
On Oct 13, 2009, at 5:16 AM, David Ruggles wrote:
> I like the shortest version of file extensions possible so I say +1 to
> Chip's suggestion as well.
>
I like the shortest version of file extensions possible so I say +1 to
Chip's suggestion as well.
Thanks,
David Ruggles
CCNA MCSE (NT) CNA A+
Network EngineerSafe Data, Inc.
(910) 285-7200 da...@safedatausa.com
-Original Message-
From: Rony G. Flatscher [mailto:rony.flatsc...@
Hi Moritz,
as Chip has pointed out it is not a problem w.r.t. hashbang lines or the
like, but an attempt to get at unique filetypes that one can then use to
associate icons with filetypes.
> I would not use file extensions that are longer than 3 characters - it's
> just not handy when working wi
