Forwarded message:
> I notice a difference between 2.1.6 and 2.2.0 on SUN4 in what is returned
> from a listbox:
>
> 2.1.6:
"reads" the string and tries to convert it into data. (Which is fine if it
was data to start with...)
> 2.2.0:
returns the actual string that was in the list box.
> Does anyone know why this change was made?
I can guess. It is a _royal_ pain when the interpreter tries to convert
strings in listboxes into lists/atoms/whatever. You have to crunch the
strings you want to put into the listbox to make sure they don't cause
errors when they're returned. If you want to put a string in a listbox
that's not a legal scheme structure you're just plain out of luck. This
behavior caused me several days of puzzlement before I figured out what was
going on. I put a string in, and I wanted a string back -- and it usually
worked, but strings with #'s in them acted very strange.
Thank-you, thank-you, thank-you for this change! This alone is worth
upgrading to 2.2.
> Is there a way to extract the data that was originally inserted?
(read-from-string value-returned-from-listbox)
--
Grant Edwards
Rosemount Inc.
grante_at_rosemount.com
Received on Thu Aug 17 1995 - 02:29:40 CEST