Group - I just sent (this morning) some code samples as part of
a mailing to this list. At least one person has received it
with the code samples having been mangled in the process (the
copy I get of outgoing mail is correct - the copy he received
is not!).
I'm now wondering if this is something done at my end by my
mailer (evolution) or something at the other end. If you
got a mangled copy, would you let me know?
How to tell.
The correct version has expressions of the form:
selfMANGLED.Type()
scattered throughout, where MANAGLED should be
"$classname" (that's a dollar sign followed by the
name of a class, as in "$Class", "$A", "$B", etc.)
Hmmm, if you're getting mangled email from me, the
above lines are going to be, uh, interesting...
If you see self.Type() instead, the email you got was
mangled.
Thanks!
--
Steve Wampler <[EMAIL PROTECTED]>
National Solar Observatory
-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_______________________________________________
Unicon-group mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unicon-group
