The product I use in my mainframe-to-Un*x migrations has such drivers;
are you interested in open-source or will you pay for a product?
-Original Message-
From: David Ruggles [mailto:da...@safedatausa.com]
Sent: Thursday, July 02, 2009 07:59
To: 'Open Object Rexx Developer Mailing List'
The format() bif always gives me a bit of a headache too, which
probably why this one has been open for so long. Yes, your
interpretation is correct. The docs (and the ANSI spec) require that
the "num+0" rounding be done first, which would lose all of the "9"s
due to rounding. The Regina result
Rick,
Could you help me with this bug. I'd really like to resolve it one
way or another as it is the oldest open bug. But, every time I read I
don't even understand it.
The doc says about format():
The number is first rounded according to standard Rexx rules, as
though the operation number+0
Although the build machine is up, the KVM server is currently down. I
hope to have it back up by EOD. You will not be able to build the following:
i386 RPM
x86_64 RPM
docs
I will send out another note if it takes longer than I anticipate to get
the KVM server back up. I am upgrading it to Fedor
Sounds good from the leak point of view!
13MB sounds an awful lot for doing nothing, however ...
(The entire original Rexx interpreter and BIFs fit in 32KB, albeit with
rather brief error messages, ISTR :-))
Mike
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Mike
On Mon, Jul 6, 2009 at 5:37 PM, Mark Miesfeld wrote:
> On Mon, Jul 6, 2009 at 3:40 PM, Rick McGuire wrote:
>
>> I checked a few additional items, and this merely confirmed my
>> suspicions. The initial object heap allocation is 8Mb, plus the
>> restored image is close to 1Mb. That's 9Mb of memory
