Re: Re: Re: Interactive Emacs/Perl environment

(load-library "epl")
(load-library "perl")
(setq epl-debugging t)
(perl-eval-expression "2+2")
[download]

returns the following output (these are the relevant lines, I think):

Debugger entered--Lisp error: (wrong-type-argument sequencep t)
  signal(wrong-type-argument (sequencep t))
  (condition-case err (epl-loop) (error (epl-destroy) (signal ... ...)
+))
  (let* ((process-connection-type nil) (out ...) (epl-interp ...)) (co
+ndition-case err (epl-loop) (error ... ...)) (epl-interp-set-status (
+quote ready)) epl-interp)
  perl-interpreter-new()
  (setq perl-interpreter (perl-interpreter-new))
  (if perl-interpreter (epl-check) (setq perl-interpreter (perl-interp
+reter-new)))
  epl-init()
  (epl-eval (epl-init) nil context "do { package main; " string " }")
  perl-eval("2+2" scalar-context)
[download]

Comment on Re: Re: Re: Interactive Emacs/Perl environment Select or Download Code

Replies are listed 'Best First'.
Re: Re: Re: Re: Interactive Emacs/Perl environment by educated_foo (Vicar) on Mar 31, 2004 at 17:45 UTC
Ack. So somewhere in epl-loop, we're trying to treat 't as a sequence, but the condition-case in perl-interpreter-new is hiding where. If you can remove the condition-case and try again, you might get something more informative. Alternatively, you can instrument epl-loop by going to it and typing \C-u \C-\M-x, then step through to see where the bogosity occurs. Unfortunately, the function's sort of large, so I can't see where the error is :(.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Re: Interactive Emacs/Perl environment
by educated_foo (Vicar) on Mar 31, 2004 at 17:45 UTC

Ack. So somewhere in epl-loop, we're trying to treat 't as a sequence, but the condition-case in perl-interpreter-new is hiding where. If you can remove the condition-case and try again, you might get something more informative. Alternatively, you can instrument epl-loop by going to it and typing \C-u \C-\M-x, then step through to see where the bogosity occurs. Unfortunately, the function's sort of large, so I can't see where the error is :(.

[reply]