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 » Core: Null handling incoherent?
Re: Core: Null handling incoherent? [message #32289 is a reply to message #32284] Fri, 06 May 2011 10:43 Go to previous messageGo to previous message
kohait00 is currently offline  kohait00
Messages: 939
Registered: July 2009
Location: Germany
Experienced Contributor
that's why i tried a second version using the Null assignment (see the second patch) as the the global SetNull usage. the SetNull method as part of class interface besides IsNullInstance and Nuller ctor is not needed in that way.. it's kind a same approach as with global IsNull template.

the global template SetNull would be used by RichValue<> in GetNull(), which prevented the compile for the custom RichValue<float>.. since i couldnt specify additional operator float() in the Nuller (the idea of a template T() operator for Nuller is not practical for ambiguity reasons).

the IsNullInstance question was why there is no unique verision of IsNull API inside Value handled classes. sometimes they are IsNullInstance (which is dictated by IsNull<>) and sometimes it's IsNull, where a template specialisation is needed, like in Font..
is it legacy or should it be unified?

[Updated on: Fri, 06 May 2011 11:07]

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
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [SOLVED] String.GetCount with umlaut
Next Topic: read/write to /dev/rtp is happening .. but a small problem
Goto Forum:
  


Current Time: Tue Jul 08 03:28:07 CEST 2025

Total time taken to generate the page: 0.03802 seconds