question

Am 22.11.2006 um 10:33 schrieb Valentin Schmidt:
>
> well, but this creates an error... or do you mean, when
using an  
> alerthook that catches the error?

there are different ways of getting <Null> although
all of these must  
be considered bugs, as lingo is not supposed to return
<Null> at any  
time. it should always "translate" it to void, but
with such a  
complex app like director is, I think everybody will
understand, that  
there still are some places, where it simply slipped.

on of which is:

put call(#bogus, [])

I think, this was meant by calling a non existent handler.
you can put an object into the list, which doesn't have the
handler  
#bogus to get the same result.

sendAllSprites and sendSprite used to do the same at one
point as far  
as I remember. that was fixed.

---------------------------

   |||
ażex



_______________________________________________
dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l

Alex da Franca wrote:
> there are different ways of getting <Null>
although all of these must 
> be considered bugs, as lingo is not supposed to return
<Null> at any 
> time. it should always "translate" it to
void, but with such a complex 
> app like director is, I think everybody will
understand, that there 
> still are some places, where it simply slipped. 

I don't think the reason is because director is so
complicated. The 
reason is that if you in c++ make a "lingo
variable" and do nothing with 
it, it is <Null>.  If you want it to be void, you
actually have to 
remember to set it to void. If it were to just default to
<void> none of 
this <Null> stuff would have happened, nomatter how
complex director 
ends up being.

Bye, Lucas
_______________________________________________
dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l

Am 23.11.2006 um 10:07 schrieb Lucas Meijer:

>
> I don't think the reason is because director is so
complicated. The  
> reason is that if you in c++ make a "lingo
variable" and do nothing  
> with it, it is <Null>.

maybe complex was the wrong term, I just can figure, that
there is  
much of code to be looked through to catch all these flaws
from a  
long development history of past times

---------------------------

   |||
ażex



_______________________________________________
dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l