Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!snorkelwacker!bloom-beacon!bloom-beacon.mit.edu!sra
From: sra@lcs.mit.edu (Rob Austein)
Newsgroups: gnu.emacs.gnus
Subject: Re: Problem with byte-compile macro
Message-ID: <SRA.89Nov28123347@mintaka.lcs.mit.edu>
Date: 28 Nov 89 17:33:47 GMT
References: <RON.89Nov23162640@clarity.Princeton.EDU>
	<DEVEN.89Nov26122502@netserv2.rpi.edu>
Sender: root@athena.mit.edu (Wizard A. Root)
Distribution: gnu
Organization: ITS Preservation Society
Lines: 13
In-Reply-To: deven@rpi.edu's message of 26 Nov 89 17:24:24 GMT

Remember that macros used in functions that are byte-compiled are
expanded when the function is byte-compiled, not when the
byte-compiled form of the function is evaluated.  The interaction
between byte-compilation and the various auto-loading mechanisms
(autoload, require, and any private hacks) is complicated and arguably
incorrect for a package that's spread into multiple files like GNUS,
but the basic idea is that you'd better make sure all the relevant
macro definitions are available to macroexpand (an emacs primitive)
before attempting to byte-compile anything.

Which is what Deven said, basicly.

--Rob Austein, MIT