No, it shouldn't be a fix for the problem, though I'm suddenly unable
to reproduce the problem again...even without that fix applied.
Rick
On Fri, Apr 17, 2009 at 4:41 PM, Mark Miesfeld miesf...@gmail.com wrote:
On Fri, Apr 17, 2009 at 11:25 AM, Rick McGuire object.r...@gmail.com wrote:
For
No, it shouldn't be a fix for the problem, though I'm suddenly unable
to reproduce the problem again...even without that fix applied.
After a flurry early this morning when first installed a test .exe ... I
haven't seen one for hours. Maybe it's time-of-day dependent? Or only
when the sun
Mark,
This is probably one for you. Mike speculated that our mystery
linein() overlay problem might be caused by not being linked with the
multi threading run time library. I thought we were doing this, but
could you double check that this is really the case?
Rick
On Sat, Apr 18, 2009 at 7:45 AM, Rick McGuire object.r...@gmail.com wrote:
This is probably one for you. Mike speculated that our mystery
linein() overlay problem might be caused by not being linked with the
multi threading run time library. I thought we were doing this, but
could you
Hmmm, it could very well be that we're somehow sharing something with
the rexx.exe launcher that
we should not be sharing. I thought we had some issues, however, with
not using the MT library
when building.
Rick
On Sat, Apr 18, 2009 at 11:39 AM, Mark Miesfeld miesf...@gmail.com wrote:
On Sat,
Hello,
After following the test efforts up to now
with admiration for you guys, I thought I'd
join in and get some testing done.
My test hardware is a PowerMac G5, with
OS X 10.5 and openSuse 11.1, both have
ooRexx 3.2 installed.
However after an hour or so at this task,
I am
Rick,
Here is one reference from MSDN library under C Run-Time Libraries:
Using the statically linked CRT implies that any state information
saved by the C runtime library will be local to that instance of the
CRT. For example, if you use strtok, _strtok_l, wcstok, _wcstok_l,
_mbstok, _mbstok_l
Hello,
Klaas. wrote:
Hello,
After following the test efforts up to now
with admiration for you guys, I thought I'd
join in and get some testing done.
My test hardware is a PowerMac G5, with
OS X 10.5 and openSuse 11.1, both have
ooRexx 3.2 installed.
However after an hour
Klaas,
The code is not going to get any more mature than it is at this point.
It should be hardward agnostic, so the architecture of your machine
should not be a problem. The only reason it has not been made
available on the Mac yet is because of a lack of someone to do the
actual port. We're
Rick,
Thank you for your reaction. Well the install task will
be less easy than I hoped for but time/head permitting
I'll make the effort and see where I end up.
About me, I am an (very) old IBM Systems Programmer/System
Engineer and have earned my wings in S/360 systems support.
About me, I am an (very) old IBM Systems Programmer/System
Engineer and have earned my wings in S/360 systems support.
That does not necessarily make supporting current code
any easier but some old tricks should have remained.
Especially I have done a lot of debugging.
Chuckle ..
11 matches
Mail list logo
