From xemacs-m  Thu Jul 31 12:42:15 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 MAA18947
	for <xemacs-beta@xemacs.org>; Thu, 31 Jul 1997 12:42:13 -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 NAA07756; Thu, 31 Jul 1997 13:46:09 -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 TAA23157; Thu, 31 Jul 1997 19:41:19 +0200 (MET DST)
Received: by tomorrow.eng.ecf.teradyne.com. (SMI-8.6/SMI-SVR4)
	id TAA13711; Thu, 31 Jul 1997 19:41:17 +0200
To: Kyle Jones <kyle_jones@wonderworks.com>
Cc: 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> <QQdapf24056.199707311649@crystal.WonderWorks.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: multipart/mixed;
 boundary="Multipart_Thu_Jul_31_19:41:17_1997-1"
Content-Transfer-Encoding: 7bit
From: Adrian Aichner <aichner@ecf.teradyne.com>
Date: 31 Jul 1997 19:41:17 +0200
In-Reply-To: Kyle Jones's message of "Thu, 31 Jul 1997 12:49:24 -0400 (EDT)"
Message-ID: <rxsk9i7i0g2.fsf@tomorrow.ecf.teradyne.com>
Lines: 113
X-Mailer: Gnus v5.4.64/XEmacs 20.3(beta15) - "Berlin"

--Multipart_Thu_Jul_31_19:41:17_1997-1
Content-Type: text/plain; charset=US-ASCII

>>>>> "Kyle" == Kyle Jones <kyle_jones@wonderworks.com> writes:

    Kyle> Gary D. Foster 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)
    Adrian> (provide 'xemacs-build-report)
    >> 
    >> Just for my own edification, why do you place the (provide...) at the
    >> beginning of the file instead of at the end?  It would seem to me that 
    >> placing it at the end would ensure that the feature is only provided
    >> upon successful loading of everything in the package, and placing it
    >> at the beginning could erroneously report success when in fact it
    >> could've bombed.

    Kyle> It makes the file more readable if the provide is near the beginning.
    Kyle> Placement makes no difference for autoloaded files, as all provide
    Kyle> and defun calls within the file are unwound if the load fails.
    Kyle> This is not true if the file is loaded manually, which is a
    Kyle> further inducement to use autoloads.

Kyle,

when I `require' the `bear' feature (which contains a rather blunt
error) the feature doesn't make it onto the fetaures variable, but
definitions prior to the error remain!

So, I guess, not having a
certain feature doesn't mean that there couldn't be variables and
functions defined via an unsucessful require. Right?


--Multipart_Thu_Jul_31_19:41:17_1997-1
Content-Type: application/octet-stream
Content-Disposition: attachment; filename="*scratch*"
Content-Transfer-Encoding: 7bit

;; If you want to create a file, don't type the text in this buffer.
;; This buffer is for notes you don't want to save, and for Lisp evaluation.
;; If you want to create a file, first visit that file with C-x C-f,
;; then enter the text in that file's own buffer.

(setq load-path 
      (cons (expand-file-name "~/el/") load-path))

(require 'bear)

--Multipart_Thu_Jul_31_19:41:17_1997-1
Content-Type: text/plain; charset=US-ASCII



--Multipart_Thu_Jul_31_19:41:17_1997-1
Content-Type: application/octet-stream; type=emacs-lisp
Content-Disposition: attachment; filename="bear.el"
Content-Transfer-Encoding: 7bit


(provide 'bear)

(setq bear-a-size 10)

(defun bear-a ()
  (interactive)
  "A Bear.")

(a real error)

(setq bear-b-size 15)

(defun bear-b ()
  (interactive)
  "B Bear.")

--Multipart_Thu_Jul_31_19:41:17_1997-1
Content-Type: text/plain; charset=US-ASCII



--Multipart_Thu_Jul_31_19:41:17_1997-1
Content-Type: application/octet-stream
Content-Disposition: attachment; filename="*Hyper Apropos*"
Content-Transfer-Encoding: 7bit

Apropos search for: "bear"

* = command (M-x) or user-variable.
a = autoloaded, b = byte-compiled, i = internal, l = lambda, m = macro.

Functions and Macros:

l* bear-a                        


Variables and Constants:

   bear-a-size                   

--Multipart_Thu_Jul_31_19:41:17_1997-1
Content-Type: text/plain; charset=US-ASCII


Regards,

Adrian

--Multipart_Thu_Jul_31_19:41:17_1997-1--

