V4MD and NULL values in lists - LINGO developers please comment

[Erich Geiersberger]

At 12:37 Uhr +0100 23.11.2004, Florian Bogeschdorfer wrote:
>However Lingo programmers like to store lists in various ways. I have not
>tested famous xtras like vList, but most developers store lists in text
>members like:
>
>Member(myListStoreMember).text=myList.string
>
>And later:
>
>myList=member(myListStoreMember).value


>Now if the list contains a <Null>, the value of the member will be 0 instead
>of a list, the list is "destroyed".
>So you actually have to look before storing the list and replace the <Null>
>by "<Null>" or VOID for example.
>
>Now this is maybe not a big deal, but the <Null> in a lingo list is simply
>not a valid list value, maybe you can change that in the future to VOID
>(Valentina 2).
>Or how do other Lingo developers feel about that?


AFAIK you also can't convert lists with VOID values from a string to a value.
Not sure if vList does the trick.



>At 12:37 23.11.2004, you wrote:
>>I am having a little problem with getting records as lists containing a
>><NULL> value. Infact <NULL> is not a valid value for a lingo list.
>
>Yes, I've also had this problem before. And converting it to a string
>and comparing the string is an option, but it is neither very elegant
>nor fast.
>
>Ruslan, there is no "NULL" in Lingo at all, the only "not a value"
>name that Lingo knows is "VOID". Could you change that <NULL>
>to <VOID> in V4MD?
>
>Martin.

Yes, it should be changed to avoid damaged property lists.

Erich