Mark Dufour wrote: > >In general it's considered quite pythonic to catch exceptions :-) > >It's a particularly useful way of implementing duck typing for example. > >I'm not sure if I've got *any* code that doesn't use exceptions > >somewhere.... > > Hehe. Okay. It will probably always be the case that you have to lose > some Python features if you want the code to run really fast. I > suppose PyPy's restricted Python subset doesn't support duck typing > either. Luckily not all code is performance critical, or you could > just try and optimize some performance critical part. But anyway, I'm > starting to understand that Shed Skin should probably support > exceptions wherever possible :-) >
Ok - the point I was trying to make was that exceptions were pretty integral to Python. I accept that losing the more dynamic features of Python for 'compilation' is a possibly worthwhile tradeoff. How easy is it going to be to call your c++ code from Python (and vice versa) ? Fuzzyman http://www.voidspace.org.uk/python/index.shtml -- http://mail.python.org/mailman/listinfo/python-list