Path: ...!weretis.net!feeder9.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail
From: mitchalsup@aol.com (MitchAlsup1)
Newsgroups: comp.arch
Subject: Re: Computer architects leaving Intel...
Date: Sun, 8 Sep 2024 18:34:54 +0000
Organization: Rocksolid Light
Message-ID: <d07031d1886e22ac33196eb981d9c825@www.novabbs.org>
References: <2024Aug30.161204@mips.complang.tuwien.ac.at> <memo.20240830164247.19028y@jgd.cix.co.uk> <vasruo$id3b$1@dont-email.me> <2024Aug30.195831@mips.complang.tuwien.ac.at> <vat5ap$jthk$2@dont-email.me> <vaunhb$vckc$1@dont-email.me> <vautmu$vr5r$1@dont-email.me> <2024Aug31.170347@mips.complang.tuwien.ac.at> <vavpnh$13tj0$2@dont-email.me> <vb2hir$1ju7q$1@dont-email.me> <jwv34mgo7sz.fsf-monnier+comp.arch@gnu.org> <2024Sep5.151959@mips.complang.tuwien.ac.at> <868qw3m3iu.fsf@linuxsc.com> <e75b789245b52c2bf56cbf2ad428fa25@www.novabbs.org> <86v7z6lv3p.fsf@linuxsc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: i2pn2.org;
	logging-data="1327457"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="65wTazMNTleAJDh/pRqmKE7ADni/0wesT78+pyiDW8A";
User-Agent: Rocksolid Light
X-Spam-Checker-Version: SpamAssassin 4.0.0
X-Rslight-Site: $2y$10$s0Rr2EUeqbKoDjhzU.GgkuaaOUdBwh3oB9vMPytxKkUEpfJjLExlW
X-Rslight-Posting-User: ac58ceb75ea22753186dae54d967fed894c3dce8
Bytes: 2575
Lines: 36

On Sun, 8 Sep 2024 2:47:38 +0000, Tim Rentsch wrote:

> mitchalsup@aol.com (MitchAlsup1) writes:
>
>> On Sat, 7 Sep 2024 23:45:45 +0000, Tim Rentsch wrote:
>
>> Another issue is that main() may not have the 3 defined arguments
>> and the containing environment is not supposed to complain when
>> argc, arv, and envp are unused or even unnamed as arguments.
>
> The usual "Hello, World" program defines main() either with no
> arguments
>
>     int
>     main(){
>         ...
>     }
>
> or with two arguments
>
>     int
>     main( int argc, char *argv[] ){
>         ...
>     }
>
> and in both cases main() has defined behavior and does not
> violate the strictures of strictly conforming programs.

The Linux environment (crt0) calls main with 3 arguments.

Are you arguing that a program can be strictly conforming and
not be type safe at its call/return interfaces ??

> If the surrounding OS or whatever cannot support these, that
> doesn't change whether the program is strictly conforming.  The
> condition of being strictly conforming is a predicate on
> programs, not on implementations.