From xemacs-m  Fri Jun  6 18:38:07 1997
Received: from altair.xemacs.org (steve@xemacs.miranova.com [206.190.83.19])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id SAA18700
	for <xemacs-beta@xemacs.org>; Fri, 6 Jun 1997 18:38:06 -0500 (CDT)
Received: (from steve@localhost)
	by altair.xemacs.org (8.8.5/8.8.5) id QAA22383;
	Fri, 6 Jun 1997 16:38:28 -0700
Mail-Copies-To: never
To: xemacs-beta@xemacs.org
Subject: Re: Warsaw: SUCCESS on sparc-sun-solaris2.5
References: <kigbu5jgwdz.fsf@jagor.srce.hr>
X-Url: http://www.miranova.com/%7Esteve/
X-Face: #!T9!#9s-3o8)*uHlX{Ug[xW7E7Wr!*L46-OxqMu\xz23v|R9q}lH?cRS{rCNe^'[`^sr5"
 f8*@r4ipO6Jl!:Ccq<xoV[Qz2u8<8-+Vwf2gzJ44lf_/y9OaQ`@#Q65{U4/TC)i2`~/M&QI$X>p:9I
 OSS'2{-)-4wBnVeg0S\O4Al@)uC[pD|+
X-Attribution: sb
From: Steven L Baur <steve@xemacs.org>
In-Reply-To: Hrvoje Niksic's message of "07 Jun 1997 01:11:03 +0200"
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
Date: 06 Jun 1997 16:38:28 -0700
Message-ID: <m24tbbi9or.fsf@altair.xemacs.org>
Lines: 30
X-Mailer: Gnus v5.4.56/XEmacs 20.3(beta5)

Hrvoje Niksic <hniksic@srce.hr> writes:

>   WARNING: ---------------------------------------------------------
>   WARNING: Compiling in support for runtime error checking.
>   WARNING: XEmacs will run noticeably more slowly as a result.
>   WARNING: Error checking is on by default for XEmacs beta releases.
>   WARNING: ---------------------------------------------------------

> A question: What exactly do we get with this error checking?  I can't
> really afford the substantial slowdown in everyday work, unless it
> offers real advantages otherwise.

If you don't have problems that you cannot trace down (and fix) yourself
you probably do not need it.  The solution I use is to keep two builds
around (with --srcdir), one compiled balls-to-the-walls-mega-optimized
for day-to-day use (that's the one I'm typing in now) and a second copy
compiled with all error checking, debug, etc. turned on for debugging.

An intermediate solution if you have space for only one build is to
turn off the error checking and debug options, but leave in `-g'.
There is little pain with `-g' if you are using gcc because you can
still compile optimized.  It's not quite as good, but is passable and
the C backtraces come with line numbers so there's a chance that
enough information to figure out what went wrong will be left in a
core dump.

The extra copy costs an incremental ~30MB in disk space.
-- 
steve@calag.com baur
Unsolicited commercial e-mail will be billed at $250/message.

