[great-users] handling of 'end of line' in AttributeMapping textboxes

[Aditya Agrawal]

Dear Tivadar,

You have hit the nail on the hammer. All your observations are correct
and the advice it true :)

Thanks,
Adi

------------------------------------------
Aditya Agrawal 
mailto:aditya.agrawal at vanderbilt.edu
http://aditya.isis.vanderbilt.edu/
Institute For Software Integrated Systems (ISIS) www.isis.vanderbilt.edu

Vanderbilt University 
2015 Terrace Place 
Nashville, TN 37203
615 322 3164


-----Original Message-----
From: Tivadar Szemethy 
Sent: Thursday, March 11, 2004 11:56 AM
To: great-users
Subject: [great-users] handling of 'end of line' in AttributeMapping
textboxes

Hi,

This is just a 'feature report' FYI, if you ever happen to run into
this.

End of line characters are converted into spaces when the text in  the
AttribMapping textbox is converted into C++ code, and sometimes this can
lead into unexpected results:
I know it's rather annoying than critical, but is there any way to
prevent this behavior ?

1. If you use C++ style comments (you comment your code regularly, don't
you ?):
X = Y + 2; // here X is calculated
... all the rest of your code becomes comment

Workaround: use /* */ style comments. 

2. If you use multiple-line string constants.
Workaround: you can't use multiple line string constants. Use \n and the
like.


3. If you mistype and you get a compilation error on the GR file, in the
unlucky case you have only a line number and a 10^6 long line with all
your AttributeMapping text on it to read and find where the problem is.
Workaround: don't mistype or use several distinct Attr.Mapping boxes. I
guess their execution order is not deterministic though :) .

Tivadar
_______________________________________________
great-users mailing list
great-users at list.isis.vanderbilt.edu
http://list.isis.vanderbilt.edu/mailman/listinfo/great-users