Michael G Schwern <[EMAIL PROTECTED]> wrote: > People make mistakes. Perhaps you should produce some errors if a user > strays outside these rules. Garbage in, garbage out: Bad. Garbage in, > error out: Good.
Albeit I did write, we need a simple interface to get at runtime libs and includes, I did not think of GIGO. I have to second Michael here. Some parts of that stuff might come from user preferences and environment variables like PARROT_LIB_PATH. We can't trust that contents. I'm for a strict error checking here. A composed path/file might get it to a system() call, having gargabe like "foo;rm -rf /" inside is suboptimal. > I'll admit to not knowing the general error philosophy of Parrot ops. The standard (current) behavior doesn't catch too many errors, but we will have some Safe.pm like execution environment - later. leo
