Brian Aker wrote:
<snip>
1) Use exceptions properly. throw a BoundsException or similar when
conversion doesn't succeed. This is the "C++" way...
I wish we could, but we are still very far away from doing this. We have
to get memory allocation working first.
++
2) If we want to continue to not use exceptions, do the STL thing and
have a fail() method which returns false if the last operation did not
succceed, and have a getErrorCode() and getErrorMessage() method which
enables callers to query the object for its error information.
That works... I suspect that when we get to the point of being able to
use exceptions, I am betting we can have a new Field design by then as
well.
Ya.
Agreed. Use pointers when supplied parameters may be NULL or when you
are indicating to the called function that it is responsible for
directly manipulating memory, references otherwise...
I wonder how many cases we will find that this is required for in the
long run.
Fewer and fewer hopefully. The more we use RAII and C++ idioms, the
less we need this. Also, Bob's new memory allocator will help ;) hint,
hint...
:)
Jay
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
