<br><font size=2 face="sans-serif">Endre,</font>
<br>
<br><font size=2 face="sans-serif">How difficult will it be to write a
parser that parses strings and converts newline and other escape characters
to some escape sequence? and then when reading the string converts it back
to the correct representation?</font>
<br>
<br><font size=2 face="sans-serif">Thanks,<br>
Adi</font>
<br>
<br><font size=2 face="sans-serif">-----------------------------------<br>
Aditya Agrawal<br>
Researcher<br>
IBM T. J. Watson<br>
mailto:aagrawa@us.ibm.com<br>
+1 (914) 784-6068 (TL 863)<br>
</font>
<br>
<br><font size=2><tt>great-users-bounces@list.isis.vanderbilt.edu wrote
on 12/08/2004 02:15:53 PM:<br>
<br>
> Matt,</tt></font>
<br><font size=2><tt>> </tt></font>
<br><font size=2><tt>> Right now, the code generator doesn’t support
the usage of global <br>
> objects and Attila are working on that.</tt></font>
<br><font size=2><tt>> </tt></font>
<br><font size=2><tt>> Thanks,</tt></font>
<br><font size=2><tt>> Feng </tt></font>
<br><font size=2><tt>> </tt></font>
<br><font size=2><tt>> -----Original Message-----<br>
> From: Matthew J. Emerson <br>
> Sent: Tuesday, December 07, 2004 10:20 PM<br>
> To: udm-users; great-users<br>
> Subject: [great-users] RE: [udm-users] newlines</tt></font>
<br><font size=2><tt>> </tt></font>
<br><font size=2><tt>> > I think that's because you use DOM backend,
and Xerces removes thenewlines..</tt></font>
<br><font size=2><tt>> </tt></font>
<br><font size=2><tt>> </tt></font>
<br><font size=2><tt>> I guess I should shift this over to the GReAT
mailing list then.</tt></font>
<br><font size=2><tt>> </tt></font>
<br><font size=2><tt>> Is there a way to use something besides the DOM
backend for a GReAT <br>
> transformation, in the interest of preserving the newlines? The
<br>
> formatting of these attribute values is important in my transformation.</tt></font>
<br><font size=2><tt>> </tt></font>
<br><font size=2><tt>> --Matt</tt></font>
<br><font size=2><tt>> </tt></font>
<br><font size=2><tt>> -----Original Message-----<br>
> From: Attila Vizhanyo <br>
> Sent: Tuesday, December 07, 2004 7:45 PM<br>
> To: udm-users<br>
> Subject: RE: [udm-users] newlines</tt></font>
<br><font size=2><tt>> </tt></font>
<br><font size=2><tt>> I think that's because you use DOM backend, and
Xerces removes the newlines..</tt></font>
<br><font size=2><tt>> </tt></font>
<br><font size=2><tt>> HTH,</tt></font>
<br><font size=2><tt>> Attila</tt></font>
<br><font size=2><tt>> </tt></font>
<br><font size=2><tt>> -----Original Message-----<br>
> From: Matthew J. Emerson <br>
> Sent: Tuesday, December 07, 2004 17:46<br>
> To: udm-users<br>
> Subject: [udm-users] newlines</tt></font>
<br><font size=2><tt>> Is there some UDM issue with newlines, where
if you set a string-<br>
> valued attribute of some object in UDM to a string which includes
a <br>
> newline, the newline is removed?</tt></font>
<br><font size=2><tt>> </tt></font>
<br><font size=2><tt>> Basically, in a GReAT transformation I’m setting
an attribute to</tt></font>
<br><font size=2><tt>> </tt></font>
<br><font size=2><tt>> std::string("\n")
+ GetType(Parameter) + std::<br>
> string("\t") + std::string(Parameter.name())</tt></font>
<br><font size=2><tt>> </tt></font>
<br><font size=2><tt>> Where GetType is a function I wrote which returns
a string. <br>
> Everything works fine, but when I look at the output model of the
<br>
> transformation, all of the newlines have been stripped out of that
<br>
> attribute value.</tt></font>
<br><font size=2><tt>> </tt></font>
<br><font size=2><tt>> --Matt_______________________________________________<br>
> great-users mailing list<br>
> great-users@list.isis.vanderbilt.edu<br>
> http://list.isis.vanderbilt.edu/mailman/listinfo/great-users<br>
</tt></font>