> is considered non-NULL: zero or anything != -1? I expected the former
> (this is how the engine handles messages) while Jiri supposes the
> latter. Where is the truth?
From my testing - on external engine messages - only the 0 was handled
as not null. Everything else was considered null. Seemed
counterintuitive as well. But I don't have strong knowledge to judge. :)
I'll use { 0xff 0xff } and { 0x00 0x00 } anyway, not like { 0xab 0x45 },
that's pure non sense. And engine seems to be using that as well.
--
Mgr. Jiří Činčura
Independent IT Specialist
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
