From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Aemon Newsgroups: gmane.emacs.help Subject: Re: Difficulties byte-compiling very large .el Date: Mon, 17 Aug 2009 20:48:55 -0700 (PDT) Organization: http://groups.google.com Message-ID: <4be0bed4-b363-4d97-9d78-a9b506664f05@j21g2000yqe.googlegroups.com> References: <55615d5a-1473-43fc-9ed7-c4708974bd1a@u20g2000prg.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1250570484 27499 80.91.229.12 (18 Aug 2009 04:41:24 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 18 Aug 2009 04:41:24 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Aug 18 06:41:17 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MdGVY-00052L-73 for geh-help-gnu-emacs@m.gmane.org; Tue, 18 Aug 2009 06:41:16 +0200 Original-Received: from localhost ([127.0.0.1]:60789 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MdGVX-0005By-Ag for geh-help-gnu-emacs@m.gmane.org; Tue, 18 Aug 2009 00:41:15 -0400 Original-Path: news.stanford.edu!newsfeed.stanford.edu!postnews.google.com!j21g2000yqe.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 84 Original-NNTP-Posting-Host: 74.73.31.119 Original-X-Trace: posting.google.com 1250567335 19403 127.0.0.1 (18 Aug 2009 03:48:55 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Tue, 18 Aug 2009 03:48:55 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: j21g2000yqe.googlegroups.com; posting-host=74.73.31.119; posting-account=5MkEHAoAAACe_HRbD9ohaOl5h8MdgFny User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.13) Gecko/2009080315 Ubuntu/9.04 (jaunty) Firefox/3.0.13, gzip(gfe), gzip(gfe) Original-Xref: news.stanford.edu gnu.emacs.help:172065 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:67240 Archived-At: On Aug 14, 12:52=C2=A0pm, Xah Lee wrote: > On Aug 12, 7:50 pm, Aemon 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 tobyte-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_elispParse= r.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 inbytecompilingelisp files... nobody > seems to have answered maybe i'll take a potshot. > > i tried to download andbytecompile 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 23bytecode or vice versa? as you > might know, emacs 23 went utf-8 for internal char representation, so > thebytecode 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. > > =C2=A0 Xah > =E2=88=91http://xahlee.org/ > > =E2=98=84 Hi Xah, Thanks for taking a look. As of my previous email I'd been using exclusively emacs 22, but your mention of emacs 23 inspired me to try it out. Interestingly the byte- compile fails with a slightly different error: ../test/grammars/as3_elispParser.el:31515:33:Error: Args out of range: 256, 0, 255 - I searched the file for non-ascii characters and found none. - The source interprets just fine using eval-buffer. - The line mentioned (31515) is the second-to-last line in the file -- I don't see anything special about it. Still no luck, but I'll keep hammering on it. BTW, do you know of any other elisp sources that are so large as 31k lines?