Re: object(x) rethink

new topic     » goto parent     » topic index » view thread      » older message » newer message

There is absolutely no need to change the behavior of object().
And for having a routine that does what is being proposed 
dummy data can do that same thing.

CChris wrote:
> 
> The practice of using special values to mark routine error status, not
> properly
> initialised yet variables and other equivalent situations is a source of
> countless
> bugs, because a value is hardly ever special enough. 
> 

LOL.  "Not special enough"?  You should be able to assign it to something 
legal that will work as a starting case anyway.  If I got an uninitialized
variable in my code I hope the compiler or interpreter will tell me
before test execution.  I don't want to test for that while its executing.


Shawn

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu