unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Xah Lee <xahlee@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Difficulties byte-compiling very large .el
Date: Fri, 14 Aug 2009 09:52:13 -0700 (PDT)	[thread overview]
Message-ID: <55615d5a-1473-43fc-9ed7-c4708974bd1a@u20g2000prg.googlegroups.com> (raw)
In-Reply-To: ce4a3d55-0067-47c6-9c35-d81293320945@f37g2000yqn.googlegroups.com

On Aug 12, 7:50 pm, Aemon <aemoncan...@gmail.com> wrote:
> I've been working on a project to create an elisp target for the ANTLR
> parser-generator. Here's the project page: http://github.com/aemoncannon/antlr-elisp/tree/experimental
>
> The generated parser for ActionScript 3 is over 30k lines long and
> fails to byte-compile with the message:
> as3_elispParser.el:31515:33:Error: Invalid character: 256, #o400,
> #x100
>
> Here's the source in question:http://aemon.com/file_dump/as3_elispParser.el
>
> I don't think the error is actually related to the content of the
> file, as deleting arbitrary chunks seems to make the error go away.
>
> There are lots of "Warning: reference to free variable ...." warnings,
> but I understand where those are coming from and I'm not worried about
> them.
>
> Bear in mind there are *lots* of macros being expanded. Most of the
> forms with the prefix 'a3el' are macros.
>
> Any ideas?

i don't have much experience in byte compiling elisp files... nobody
seems to have answered maybe i'll take a potshot.

i tried to download and byte compile it, but first error is that i
lack the required package declared in the first line. So, we couldn't
really test it.

about this error:
> as3_elispParser.el:31515:33:Error: Invalid character: 256, #o400,
> #x100

are you using emacs 22 with emacs 23 byte code or vice versa? as you
might know, emacs 23 went utf-8 for internal char representation, so
the byte code produced are incompatible with emacs 22. The error msg
above smells like this sort of problem. If your .el files does not
have any non-ascii char, then it shouldn't be a problem though.

oh, just noticed you did give the project page link above. Am tired
atm will have maybe try later. But when did this problem start to
happen? There must be a point when things are working and not working.

  Xah
∑ http://xahlee.org/

  reply	other threads:[~2009-08-14 16:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13  2:50 Difficulties byte-compiling very large .el Aemon
2009-08-14 16:52 ` Xah Lee [this message]
2009-08-18  3:48   ` Aemon
2009-08-18  4:22     ` Xah Lee

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55615d5a-1473-43fc-9ed7-c4708974bd1a@u20g2000prg.googlegroups.com \
    --to=xahlee@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).