Hrvoje Niksic <hniksic(a)iskon.hr> writes in xemacs-beta(a)xemacs.org:
SL Baur <steve(a)beopen.com> writes:
> (setq R (pq-exec P "This is a bad query;"))
> #<PGresult PGRES_FATAL_ERROR - >
This should signal a real error. We've got an error system;
let's
use it. The PostgreSQL error object should be encapsulated within
the error data, so that a handler can use it.
I've cleaned this up in the version I am about to commit to the CVS
tree. XEmacs now beeps and prints `fatal error [ERROR: parser: parse
error at or near "this"] in the echo area. Errors are (or should be
unless I missed something) consistently signaled and notices are sent
via the `warn_when_safe' interface.
> DEFUN ("pq-finish", Fpq_finish, 1, 1, 0, /*
> Close the connection to the backend.
> Note: This entry point is provided for completeness, but its use is not
> recommended. The preferred way to delete connections is to let the Emacs
> garbage collection mechanism do it.
I agree with Jan about this. GC is there to manage memory;
programmers who rely on GC to clean up all the resources could be
called lazy at best.
The crashes have been fixed, so the comment you are citing is now
inoperative in the version that will go into CVS.