Hi Marino > Suppose I want to map from OpenDBX errors to SqueakDBX exceptions, I have > to do it with the index of the array then. So, if you then change, reorder > or whatever you do with the array, I will map wrong exceptions :(
That won't happen until 2.0 as I would break binary compatibility to all applications - and OpenDBX 2.0 won't be started even in the not so near future if you have a look at the roadmap in the wiki. > It would be grate to define static numbers. I mean, numbers that do not > change. This is the case. > Right now in SqueakDBX you rise a generic OpenDBXException which has a > instance variable which is the number. > But, perhaps, if a future I want to reify the exceptions, for example > OpenDBXNoMemoryException. For that work, I think I will wait for OpenDBX > 2.0 if they numbers won't change. No, I don't think one type of exception per error code is a good idea. There will be also only one exception in 2.0 - but there's a long way to go until reaching that point ;-) Norbert -- OpenPGP public key http://www.linuxnetworks.de/norbert.pubkey.asc
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf
_______________________________________________ libopendbx-devel mailing list libopendbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libopendbx-devel http://www.linuxnetworks.de/doc/index.php/OpenDBX
