[eluser]joelkallman[/eluser]
@Aken, I agree that for big releases it is acceptable to create breaking changes within the code. So my question to everybody, if this is worth breaking code for, what are the <b>functional benefits</b> within CodeIgniter (or PHP) that returning NULL will produce? Let me list what I've seen already.
We have (1) simplifying some conditional statements (although it will break others that currently do strict FALSE checks) and (2) simplifying conditional statements for database inserts/updates where you want to pass NULL for a particular field (which requires that that field can store NULL) if it is not found.
Since there are a lot of people who agree with changing FALSE to NULL, I must be missing some areas of CodeIgniter (or PHP) where NULL produces an amazing benefit.
If you'd all be so kind, I'd love to hear your thoughts on the functional benefits of this change.
