Deutsch   English   Français   Italiano  
<vhpogu$14mb6$1@dont-email.me>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!eternal-september.org!feeder2.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Bart <bc@freeuk.com>
Newsgroups: comp.lang.c
Subject: Re: else ladders practice
Date: Fri, 22 Nov 2024 11:05:02 +0000
Organization: A noiseless patient Spider
Lines: 52
Message-ID: <vhpogu$14mb6$1@dont-email.me>
References: <3deb64c5b0ee344acd9fbaea1002baf7302c1e8f@i2pn2.org>
 <vg37nr$3bo0c$1@dont-email.me> <vg3b98$3cc8q$1@dont-email.me>
 <vg5351$3pada$1@dont-email.me> <vg62vg$3uv02$1@dont-email.me>
 <vgd3ro$2pvl4$1@paganini.bofh.team> <vgdc4q$1ikja$1@dont-email.me>
 <vgdt36$2r682$2@paganini.bofh.team> <vge8un$1o57r$3@dont-email.me>
 <vgpi5h$6s5t$1@paganini.bofh.team> <vgtsli$1690f$1@dont-email.me>
 <vhgr1v$2ovnd$1@paganini.bofh.team> <vhic66$1thk0$1@dont-email.me>
 <vhins8$1vuvp$1@dont-email.me> <vhj7nc$2svjh$1@paganini.bofh.team>
 <vhje8l$2412p$1@dont-email.me> <vhl1up$5vdg$1@dont-email.me>
 <vhlg53$8lff$1@dont-email.me> <vhnasl$l8h5$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 22 Nov 2024 12:05:02 +0100 (CET)
Injection-Info: dont-email.me; posting-host="373db3823bc9f838b9ab0e3fdedd4a11";
	logging-data="1202534"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19jO3KAfQDM5K/s5VKO1Gj9"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:LGjUIUqe+DVOz6BDqej8AsIDYRY=
In-Reply-To: <vhnasl$l8h5$1@dont-email.me>
Content-Language: en-GB
Bytes: 3576

On 21/11/2024 13:00, David Brown wrote:
> On 20/11/2024 21:17, Bart wrote:

> Your development process sounds bad in so many ways it is hard to know 
> where to start.  I think perhaps the foundation is that you taught 
> yourself a bit of programming in the 1970's,

I did a CS degree actually. I also spent a year programming, working for 
the ARC and SRC (UK research councils).

But since you are being so condescending, I think /your/ problem is in 
having to use C. I briefly mentioned that a 'better language' can help.

While I don't claim that my language is particularly safe, mine is 
somewhat safer than C in its type system, and far less error prone in 
its syntax and its overall design (for example, a function's details are 
always defined in exactly one place, so less maintenance and fewer 
things to get wrong).

So, half the options in your C compilers are to help get around those 
shortcomings.

You also seem proud that in this example:

   int F(int n) {
       if (n==1) return 10;
       if (n==2) return 20;
   }

You can use 'unreachable()', a new C feature, to silence compiler 
messages about running into the end of the function, something I 
considered a complete hack.

My language requires a valid return value from the last statement. In 
that it's similar to the Rust example I posted 9 hours ago.

Yet the gaslighting here suggested what I chose to do was completely wrong.

> And presumably you also advise doing so on a bargain basement 
> single-core computer from at least 15 years ago?

Another example of you acknowledging that compilation speed can be a 
problem. So a brute force approach to speed is what counts for you.

If you found that it took several hours to drive 20 miles from A to B, 
your answer would be to buy a car that goes at 300mph, rather than doing 
endless detours along the way.

Or another option is to think about each journey extremely carefully, 
and then only do the trip once a week!