I have a Rexx program that merges several small files onto
one large one. As it turned out a few of the small files were
prefixed with a UTF8 BOM, |0xEFBBBF|. Should the BOM
have been recognized and discarded?
This is on Windows Server 2003 running ooRexx 4.1.0.
Here is the part of the code that
that a BOM should be checked for, even if it is ignored. Or a error
issued for an
unsupported encoding. For UTF8 I would ignore it and process the file as
ASCII.
James Johnson
--
Lotusphere 2011
Register now
is just another form
of a SubCom environment. The command address rxpipe works and
invokes my sub command handler.
If the Address command recognizes my environment, why doesn't
RxSubCom Query?
James Johnson
Okay, I can accept that.
Is there a way to test if a DIRECT_ENVIRONMENT is available?
I could issue some command and check the return code. But how do
I tell the difference between an unregistered environment, RC=30, and a
command
handler error which could also be 30?
James Johnson
Rick
.
4) Enter Trace Off a second time and it is honored. Tracing ends and
program runs to completion.
I used the qdate.rex program for my testing and issued the Trace Off
commands
while in the init routine.
James Johnson
Consider the following:
1) Open a terminal session. Your are in some directory that we will call
home.
2) Within the home directory is a sub directory dirA.
3) Within dirA' is a sub directory dirB.
4) Within dirA is a rexx program named progA.
5) progA calls progB which resides in dirB.
a
different thread will fail.
James Johnson
Rick McGuire wrote:
Sorry, but no. If we add this, then this is something that will need
to be supported forever, and I'm just not going to deal with it. This
is not something we can support, particularly when the request comes
right before
is in effect
When set to FALSE the thread is not validated.
It would then be the application developers responsibility for any
conflicts that would arise
when running with this option set to FALSE.
James Johnson
Rick McGuire wrote:
On Thu, May 21, 2009 at 11:11 AM, Mark Miesfeld miesf...@gmail.com wrote
I went back and check my source code and I supply an extension on the first
invocation. When I remove the extension it fails with error code 3001.
Do you still need a sample program?
Rick McGuire wrote:
James,
The CallProgram() API was not performing any path or extension
resolution at all,
I have a library that implements CMS/TSO Piprlines support for the PC.
I have interfaced this library to ooRexx 4.0. To accomplish this I had
to make so changes
to the 4.0 beta.
1) The interface is thru a SubCom environment. I had to modify the
subcom CommandHandler to
pass a CallContext
10 matches
Mail list logo
