Is this a bug in elisp

[santanu]

Hello Everybody,

I am using GNU Emacs-22.1.50.1 (Ubuntu 7.10). I was having some
problems with the verilog-mode in this version of Emacs (although
it worked perfectly in Emacs-21.x). It seems that I found the location
of the problem. But since I don't know elisp, I am unable to
understand
the cause of the problem. So I am just inserting below what I think
is the relevant portion of the code:

-----------------------------------------------
(define-skeleton verilog-sk-prompt-msb
  "Prompt for least significant bit specification."
  "msb:" str & ?: & (verilog-sk-prompt-lsb) | -1 )

(define-skeleton verilog-sk-prompt-lsb
  "Prompt for least significant bit specification."
  "lsb:" str )
-----------------------------------------------

I just defined those functions above in the *scratch*
buffer. Then tried to evaluate (verilog-sk-prompt-msb).
Instead of the expected result, I am placed in a debug
buffer with the following content I cannot figure out:
(Doing the same in emacs-21.x does not cause any
problem)
--------------------------------------------------
Debugger entered--Lisp error: (error "Lisp nesting exceeds `max-lisp-
eval-depth'")
  skeleton-internal-1(t t nil)
  skeleton-internal-1(t t nil)
  skeleton-internal-1(t t nil)
  ....
  ....
  skeleton-internal-1(t t nil)
  skeleton-internal-1(t t nil)
  skeleton-internal-1((verilog-sk-prompt-lsb) nil nil)
  byte-code("Ã@Ã       #‡" [skeleton recursive skeleton-internal-1
nil] 4)
  skeleton-internal-list(("msb:" str & 58 & (verilog-sk-prompt-lsb) |
-1) nil)
  (let nil (skeleton-internal-list skeleton str))
  eval((let nil (skeleton-internal-list skeleton str)))
  skeleton-insert(("msb:" str & 58 & (verilog-sk-prompt-lsb) | -1) nil
nil)
  skeleton-proxy-new(("msb:" str & 58 & (verilog-sk-prompt-lsb) | -1)
nil nil)
  verilog-sk-prompt-msb()
  eval((verilog-sk-prompt-msb))
  eval-last-sexp-1(nil)
  eval-last-sexp(nil)
  call-interactively(eval-last-sexp)
--------------------------------------------------------

I feel like I am getting into an endless recursion here. Dunno how.
It would be very helpful if anyone could suggest/provide a fix.

Thanks in advance for your help.

Regards,
Santanu Chatterjee