[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Some issues with error conditions
From: |
Dmitriyi Paduchikh |
Subject: |
Some issues with error conditions |
Date: |
Mon, 11 Jul 2005 20:34:50 +0600 |
User-agent: |
Gnus/5.110003 (No Gnus v0.3) |
Hello,
Evaluating expression
(let ((process (start-process "false" nil "false")))
(sleep-for 1)
(process-send-string process "Hi there!"))
produces an error of most general kind:
Debugger entered--Lisp error: (error "Process false not running")
process-send-string(#<process false> "Hi there!")
(let ((process ...)) (sleep-for 1) (process-send-string process "Hi there!"))
eval((let ((process ...)) (sleep-for 1) (process-send-string process "Hi
there!")))
eval-last-sexp-1(nil)
eval-last-sexp(nil)
call-interactively(eval-last-sexp)
Shouldn't it be something like process-error instead? IMHO signalling
general error in this situation makes catching of errors related with
processes more difficult.
And also end-of-file (end of file during parsing),
invalid-read-syntax, scan-error (not sure about this) probably might
be all in the category parse-error as such condition already exists.
--
Dmitriyi Paduchikh
- Some issues with error conditions,
Dmitriyi Paduchikh <=