Yes, I agree. But there needs to be a good design how to store and use those, anyway.
Actually, I think I would prefer a very clear and precise syntax, like
try <statement> catch [(Exception e)] { File_Error: ... break; Compile_Error: ... break; }
but I suspect it's not practical enough. And anyway, any good exception handling sugar is good enough for me...
/ Mirar
Previous text:
2003-10-01 22:48: Subject: Re: throw or return
Ok, I'll change "very rarely" to "only sometimes": That approach doesn't work very well with subgroups. Say for instance that errors are classified as "os", "pike", etc and that "os" errors are further classified into "io", "memory", etc. How would you then write a switch that handles "io" and "pike" errors but not anything else?
/ Martin Stjernholm, Roxen IS