Path: csiph.com!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c,comp.unix.programmer Subject: Re: Experimental C Build System Date: Sat, 03 Feb 2024 14:02:39 -0800 Organization: None to speak of Lines: 42 Message-ID: <87r0htmcjk.fsf@nosuchdomain.example.com> References: <20240202104933.269@kylheku.com> <20240202222935.691@kylheku.com> MIME-Version: 1.0 Content-Type: text/plain Injection-Info: dont-email.me; posting-host="026cbd12272797f54d5c091ea0e8c8d6"; logging-data="3473395"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/xdh3WS7P8Stg9t+85vzV4" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) Cancel-Lock: sha1:hOdeQctLPiIK1f8hUOXY8inPORE= sha1:QlCRTlyVK44+6JxFgFQAUKDFWgc= Xref: csiph.com comp.lang.c:381709 comp.unix.programmer:15163 Malcolm McLean writes: [...] > as is a development tool. So there are two aspects to it. The first is > deploying as itself. It must be available and capable of being invoked > on all machines where it needs to be available. It mustn't refuse to > run correctly because some path somewhere is not set up or it doesn't > have write permission to output an executable, and so on. That may > well have been achieved. Typing "as" into the shell on the computer > I'm typing this on does indeed invoke the program. > > But the other side to it that as must make it easy to deploy the > actual useful end user programs that it is used to develop. So if we > write an as script, it must be easy to make that script part of an > executable, place it on the user's machine, and set it up so that the > user can easily run it and play space invaders or achieve whatever > else he ultimately wishes to achieve. And what Bart is saying is that > that is where as is falling down. "as", as typically provided on Unix-like systems, has a command-line interface that bart finds distasteful. There is nothing bart wants to do that he can't do with the as interface, but he doesn't like the way he has to do it. He has made the false claim that there's something seriously wrong with "as". (It does have its quirks, but those quirks are easy to work around, or even to use as intended.) > I don't use as myself, so it's hard to commment on the specifics. But > from experience with similar systems, this will be where the problems > lie. The complaint sems to be that because of the quirky way in which > it matches up scripts to output executables, it's too hard to package > the scripts so that they are assembled correctly. Since as I say I > don't use as I can't comment on that directly, but I can well believe > it. So you've simply assumed, without evidence, that the "as" command line interface causes all these problems. It doesn't. -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com Working, but not speaking, for Medtronic void Void(void) { Void(); } /* The recursive call of the void */