Is this the expected behaviour when accidentally choosing a directory as the master?
% pike -m . /home/mirar/pike/src/object.c:477: Fatal error: low_read_file(.) failed, errno=21 No stack - no backtrace. zsh: abort pike -m .
Hardly. (Why would it be?)
/ Martin Stjernholm, Roxen IS
Previous text:
2004-05-31 10:31: Subject: expected?
Is this the expected behaviour when accidentally choosing a directory as the master?
% pike -m . /home/mirar/pike/src/object.c:477: Fatal error: low_read_file(.) failed, errno=21 No stack - no backtrace. zsh: abort pike -m .
/ Mirar
Because error 21 is "EISDIR", which is what you're supposed to get when trying to use a directory as a file? Also, error handling can be expected to be a bit "rough" before the master is loaded, since the master is supposed to handle most of it.
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2004-05-31 16:05: Subject: expected?
Hardly. (Why would it be?)
/ Martin Stjernholm, Roxen IS
Pike should fail fatally only for internal errors. That error isn't internal.
/ Martin Stjernholm, Roxen IS
Previous text:
2004-05-31 22:07: Subject: expected?
Because error 21 is "EISDIR", which is what you're supposed to get when trying to use a directory as a file? Also, error handling can be expected to be a bit "rough" before the master is loaded, since the master is supposed to handle most of it.
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Now you're talking about how it _should_ be, not how we're expecting it to be. :-)
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2004-05-31 22:53: Subject: expected?
Pike should fail fatally only for internal errors. That error isn't internal.
/ Martin Stjernholm, Roxen IS
pike-devel@lists.lysator.liu.se
-
Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum -
Martin Stjernholm, Roxen IS ＠ Pike developers forum
-
Mirar ＠ Pike developers forum