Comments on: Types in Quest 5.0 http://www.axeuk.com/blog/2010/02/18/types-in-quest-5-0/ Quest updates, tips and information, plus news about the wider interactive fiction world Sat, 20 Mar 2010 17:47:29 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Alex Warren http://www.axeuk.com/blog/2010/02/18/types-in-quest-5-0/comment-page-1/#comment-299 Alex Warren Tue, 23 Feb 2010 19:01:58 +0000 http://www.axeuk.com/blog/?p=112#comment-299 Actually that info on the wiki is out of date - there's no IsNull function any more. You can just check for equality with null as normal, e.g. "if (object = null) ..." Actually that info on the wiki is out of date – there’s no IsNull function any more. You can just check for equality with null as normal, e.g. “if (object = null) …”

]]> By: Jon D. (Overcat) http://www.axeuk.com/blog/2010/02/18/types-in-quest-5-0/comment-page-1/#comment-298 Jon D. (Overcat) Tue, 23 Feb 2010 10:48:36 +0000 http://www.axeuk.com/blog/?p=112#comment-298 Hmm. Perhaps it is best to leave the two as distinguishable. I guess that's why you have Quest defining the IsNull function? Hmm. Perhaps it is best to leave the two as distinguishable. I guess that’s why you have Quest defining the IsNull function?

]]> By: Alex Warren http://www.axeuk.com/blog/2010/02/18/types-in-quest-5-0/comment-page-1/#comment-297 Alex Warren Mon, 22 Feb 2010 21:15:47 +0000 http://www.axeuk.com/blog/?p=112#comment-297 A drawback I see is that it makes it impossible to tell if the object actually has a null value for a boolean, or if it's genuinely a boolean false. A drawback I see is that it makes it impossible to tell if the object actually has a null value for a boolean, or if it’s genuinely a boolean false.

]]> By: Jon D. (Overcat) http://www.axeuk.com/blog/2010/02/18/types-in-quest-5-0/comment-page-1/#comment-275 Jon D. (Overcat) Thu, 18 Feb 2010 11:42:54 +0000 http://www.axeuk.com/blog/?p=112#comment-275 Regarding null: I think the default type might expand proportionally to the complexity of the world model if null != false. After all, you'd have to explicitly set new properties to false in the default type as the model grew. What are some of the foreseeable drawbacks of equating null to false in expressions? Regarding null:

I think the default type might expand proportionally to the complexity of the world model if null != false. After all, you’d have to explicitly set new properties to false in the default type as the model grew.

What are some of the foreseeable drawbacks of equating null to false in expressions?

]]>