On 22/01/2016 01:40, Marvin Humphrey wrote:
Finally, working with the Python error mechanism has reinforced my opinion that if Clownfish is to be a "least-common-denominator" object model, maximally compatible with as many hosts as possible, it should prefer return codes over exceptions -- because return codes are easy to transform into exceptions, but exceptions are hard to turn into return codes.
I agree. I'd still like to keep the current exception mechanism as an alternative. It makes development of Clownfish projects much easier. If we only use exceptions for unrecoverable errors, memory leaks shouldn't be a problem.
Nick
