From xemacs-m  Wed Jul 30 17:04:04 1997
Received: from steadfast.teradyne.com (steadfast.teradyne.com [131.101.1.200])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id RAA10996
	for <xemacs-beta@xemacs.org>; Wed, 30 Jul 1997 17:04:03 -0500 (CDT)
Received: from engine.ecf.teradyne.com (engine.ecf.teradyne.com [131.101.192.6]) by steadfast.teradyne.com (8.7.1/8.7.1) with ESMTP id SAA02126 for <xemacs-beta@xemacs.org>; Wed, 30 Jul 1997 18:08:18 -0400 (EDT)
Received: from tomorrow.eng.ecf.teradyne.com. (tomorrow.ecf.teradyne.com [131.101.192.7]) by engine.ecf.teradyne.com (8.7.1/8.7.1) with SMTP id AAA20869; Thu, 31 Jul 1997 00:03:29 +0200 (MET DST)
Received: by tomorrow.eng.ecf.teradyne.com. (SMI-8.6/SMI-SVR4)
	id AAA12097; Thu, 31 Jul 1997 00:03:26 +0200
To: xemacs-beta@xemacs.org
Subject: Re: How to determine build-dir within running XEmacs?
References: <rxszprrme68.fsf@ecf.teradyne.com> 	<199707131143.EAA02550@xemacs.eng.sun.com> 	<lbk9iu1hr1.fsf@boron.kurims.kyoto-u.ac.jp> 	<rxsg1th7mbn.fsf@midnight.ecf.teradyne.com> <199707150324.MAA21551@boron.kurims.kyoto-u.ac.jp> <rxszpr4e0xz.fsf@tomorrow.ecf.teradyne.com> <bci4t9c9shv.fsf@corp.Sun.COM>
X-Face: 4[iHdXiTu\V3u[~\I)<f9HC);%~nG8`oUqv#uzvs6=\V{AjN6Sn
 c/qi;YLwRmEbt8Y*=j5n(urqY@chPh@J'D"QlqD!C8>*}#kYF[-tYl3VZga/HSOP|K,{L
 Rtu@f0y/=O&Cu}\:~d|P$JON?pn?j,&CnPb1z#/TL9bkAJwyol&a:SvYj-VYbM=Dtxhk9
 =w|R6U3_;SH&B<Mfy6Q%#
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=ISO-8859-1
From: Adrian Aichner <aichner@ecf.teradyne.com>
Date: 31 Jul 1997 00:03:25 +0200
In-Reply-To: Gary.Foster@Corp.Sun.COM's message of "30 Jul 1997 13:47:56 -0700"
Message-ID: <rxsvi1sdwpe.fsf@tomorrow.ecf.teradyne.com>
Lines: 46
X-Mailer: Gnus v5.4.64/XEmacs 20.3(beta15) - "Berlin"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by xemacs.org id RAA10997

>>>>> "GDF" == Gary D Foster <Gary.Foster@Corp.Sun.COM> writes:

>>>>> "Adrian" == Adrian Aichner <aichner@ecf.teradyne.com> writes:
    Adrian> if you want to give it a try with an updated version of
    Adrian> xemacs-build-report.el, here it is.

    Adrian> (require 'config) (provide 'xemacs-build-report)

    GDF> Just for my own edification, why do you place the
    GDF> (provide...) at the beginning of the file instead of at the
    GDF> end?  It would seem to me that placing it at the end would
    GDF> ensure that the feature is only provided upon successful
    GDF> loading of everything in the package, and placing it at the
    GDF> beginning could erroneously report success when in fact it
    GDF> could've bombed.

Gary,

I haven't done this for a particular reason. The Lispref index entry
provide gives a good run-down on autoload vs. provide/require.

It doesn't recommend where to place the provide form.
lisp/modes/*.el don't reveal a uniform usage either.

If one of the fetaures writers for XEmacs could shed some light on
this it might even be a good candidate to include in the lispref
section mentioned above.

Cheers,

Adrian

    GDF> Of course, I don't _really_ know, which is why I'm asking...

    GDF> -- Gary F.



-- 
                            Adrian Aichner
                        Applications Engineer
  Teradyne GmbH
  Semiconductor Test Group    Telephone +49/89/41861(0)-208
  Dingolfinger Strae 2       Fax       +49/89/41861-217
  D-81673 MNCHEN             E-mail    aichner@ecf.teradyne.com

