Talk:Undefined values: Difference between revisions

From Rosetta Code
Content added Content deleted
(Not sufficiently distinct from the NULL task)
 
m (NULL is a macro, Null is a task)
Line 1: Line 1:
After discussion on IRC, it was noted that "undefined" as this task is not significantly disctinct from NULL. However, I prefer this task's "identify and exercise the mechanisms" approach, as opposed to [[NULL]]'s more specific "check" approach. I'm certainly open to other's thoughts on how to effect improvement of the NULL task, make this task sufficiently distinct, or possibly deprecate that task. --[[User:Short Circuit|Michael Mol]] 03:04, 28 November 2009 (UTC)
After discussion on IRC, it was noted that "undefined" as this task is not significantly distinct from NULL. However, I prefer this task's "identify and exercise the mechanisms" approach, as opposed to [[Null]]'s more specific "check" approach. I'm certainly open to others' thoughts on how to effect improvement of the NULL task, make this task sufficiently distinct, or possibly deprecate that task. --[[User:Short Circuit|Michael Mol]] 03:04, 28 November 2009 (UTC)

Revision as of 03:23, 28 November 2009

After discussion on IRC, it was noted that "undefined" as this task is not significantly distinct from NULL. However, I prefer this task's "identify and exercise the mechanisms" approach, as opposed to Null's more specific "check" approach. I'm certainly open to others' thoughts on how to effect improvement of the NULL task, make this task sufficiently distinct, or possibly deprecate that task. --Michael Mol 03:04, 28 November 2009 (UTC)