indent-new-comment-line misbehaviour?

[Uwe Brauer]

>>>>> "Stephen" == Stephen J Turnbull <stephen at xemacs.org> writes:

   > First things first.  A patch to 21.5 may fail to apply to 21.4, but
   > you can probably get a copy of 21.5 version of that function from
   > http://hg.debian.org/hg/xemacs/xemacs, and put the defun in init.el,
   > where it will override the built-in.

   > Second, I see that this comes from something called "newcomment.el",
   > so it may not work at all without the rest of the new comment stuff.
   > You may copy that whole file to ~/.xemacs and put

   >     (load (expand-file-name "~/.xemacs/newcomment.elc"))


Okay some (bad) news for 21.4.

Byte compiling newcomment.el gave me
(void-function declare-fboundp)
Compiling file /home/oub/newcomment.el at Tue Jan 22 14:40:47 2008
While compiling the end of the data:
  ** the function declare-fboundp is not known to be defined.


So when I loaded the file and executed  `indent-new-comment-line'
no surprise that I got an error which I attach.

Now the big question, I found out that declare-fboundp is defined in 
bytecomp-runtime.el:

So either I could use the whole bytecomp-runtime or just catch declare-fboundp 
any advice?

Uwe 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: newcomment-bug
Type: application/octet-stream
Size: 4118 bytes
Desc: not available
Url : http://lists.xemacs.org/pipermail/xemacs-beta/attachments/20080122/490c184c/newcomment-bug.obj