Here's the file you need - output.cpp (based on 0.51). Tom will probably
want to change the layout of this. Your test xml and xsl script work fine
with the changed code.
The change points at the compiler not doing the right thing. I will be
sending a bug report to IBM about this, as passing an anonymous object on
the stack into another method using a const reference parameter should be
okay. We have a lot of code which does this! I put breakpoints on the Str
constructors to watch execution when returning from getAliasedName. I didn't
hit any breakpoint, so the returned Str wasn't being constructed properly.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 23, 2001 5:03 PM
To: Sablotron Mailing List
Subject: Re: [Sab] Problem with OutputterObj::eventElementEnd on IBM
AIX..
Thanks Tim and Tom for the great help.
I was going to work on the code as soon as I got a chance, but if you guys
get to it first (as it appears you are) then we'd be happy to test it here
with quick turn around time and also in the future assist with supporting
AIX. Just let me know how to get the code if its ready.
Herman Walker
General Dynamics
Gulfstream Aerospace
www.gulfstream.com
Tom Kaiser <[EMAIL PROTECTED]> on 02/23/2001 04:57:25 PM
Please respond to [EMAIL PROTECTED]
To: Sablotron Mailing List <[EMAIL PROTECTED]>
cc:
Subject: Re: [Sab] Problem with OutputterObj::eventElementEnd on IBM AIX..
Fickle indeed! I did it the way you mention below. I also removed those
includes of iostream.h - it's in the cvs.
Tom
Tim Crook wrote:
> Hi Tom.
>
> The VisualAge compiler on IBM AIX seems very fickle. Argh!
>
> The compiler will do the right thing with this:
> Str temp;
> if (physical)
> {
> temp = proc -> getAliasedName(name, currNamespaces);
> physical -> outputElementEnd(temp, 0);
> };
> ...
output.cpp
