On 15/08/06, Edward Slattery <[EMAIL PROTECTED]> wrote:
OK, so if we dont deal with exception hiding, the two are:
Employee employee = someSDOmethod_returningMyTypesafeDO();
cout << employee->getName() << endl;
DataObjectPtr employee = someSDOmethod_returningAnSDO();
if (employee)
{
cout << employee->getString("name") << endl;
}
is necessary.
..so Im not sure that type safety really increases maintainability that
much that a developer would be willing to introduce a custom step into the
build process, and maintain generated code with all the resulting issues
of
upward compatibility, debugging code you didn't write, getting inevitable
bugs fixed in the generator in a timely way etc.
Im not saying typesafe is wrong, I just dont want to see it developed in
the
C++ world because its cool in the java world.
Theres no design for it yet - but maybe the value in doing it will become
clearer to me if we start discussing that amongst the community.
Absolutely. Unless there is a valid use case then we shouldn't go ahead and
implement it.
--
Pete
