From mboxrd@z Thu Jan  1 00:00:00 1970
From: dexen deVries <dexen.devries@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Date: Thu,  3 Feb 2011 11:27:17 +0100
User-Agent: KMail/1.13.5 (Linux/2.6.37-rc6-18+; KDE/4.5.5; x86_64; ; )
References: <ab1fa28a4c73d7daa499f28972965822@hamnavoe.com>
In-Reply-To: <ab1fa28a4c73d7daa499f28972965822@hamnavoe.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <201102031127.18004.dexen.devries@gmail.com>
Subject: Re: [9fans] HELP: recoving important header file rudely clobbered
Topicbox-Message-UUID: aa364136-ead6-11e9-9d60-3106f5b1d025

On Thursday, February 03, 2011 11:24:53 am dexen wrote:
> On Thursday, February 03, 2011 11:16:05 am Richard Miller wrote:
> > > %: %.$O
> > >=20
> > >         $LD $LDFLAGS  -o $target $prereq
>=20
> Perhaps wont' be a problem with mk(1), but make(1) had biten me more than
> once with a rule like `-o $SOMEOUTPUT $SOMESOURCES'. When $SOMEOUTPUT was
> empty... the source file that had the bad luck of being the first on
> $SOMEOUTPUT got overwritten.
>=20
> tl;dr: put -o $SOMEOUTPUT last in a recipe, at least for make(1)

edit:
the first on $SOMESOURCES* got overwritten

=2D-=20
dexen deVries

[[[=E2=86=93][=E2=86=92]]]

> how does a C compiler get to be that big? what is all that code doing?

iterators, string objects, and a full set of C macros that ensure
boundary conditions and improve interfaces.

ron minnich, in response to Charles Forsyth

http://9fans.net/archive/2011/02/90