Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ Core » The problem with 'Null'
Re: The problem with 'Null' [message #20452 is a reply to message #20450] Thu, 19 March 2009 09:20 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 13980
Registered: November 2005
Ultimate Member
cbpporter wrote on Thu, 19 March 2009 03:45


There are of course exceptions. Things like Size and Point will not be initialized by default construction and can result in bugs if the user is not aware of this fact.



Well, that depends on definition of "initialized" Wink

Is normal scoped

{
    int x;


initialized or not? I believe in sense it is - all resources required for it are allocated and it is ready to be used. Of course, contract does not define any particular initial value for it Smile

(I agree this is mostly just pointless word-play).

Mirek

[Updated on: Thu, 19 March 2009 09:20]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: In some cases CParser can be out of buffer
Next Topic: Possible bug/clarification only callback2 was changed for const Object*
Goto Forum:
  


Current Time: Sat Jun 01 06:43:33 CEST 2024

Total time taken to generate the page: 0.01791 seconds