Re: Bug with `scan-sexps' / syntax tables in XEmacs-21.4.2

Bring up a java-mode (or JDE) buffer and insert this into it: public class Foo { class Bar // foo. { class Baz { /* foo. */ int flobble (String foo) { } } } } Note that the second closing parenthesis is believed (by, for instance, `(goto-char (scan-sexps (point) -1))') to match the very first open parenthesis, and that deleting either of the comments corrects this misbehaviour. Am I right that this can only reasonably be interpreted as a bug in the XEmacs C core, or is it something completely different?