Path: ...!Xl.tags.giganews.com!local-3.nntp.ord.giganews.com!nntp.earthlink.com!news.earthlink.com.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 12 Feb 2025 22:09:22 +0000
Subject: Re: GIMP 3.0.0-RC1
Newsgroups: comp.os.linux.misc,comp.os.linux.advocacy
References: <vkjmdg$30kff$1@dont-email.me> <vl93dl$3vkun$1@dont-email.me>
 <vl9449$3vo6h$3@dont-email.me> <vl9aov$pp7$1@dont-email.me>
 <vla4hr$5n4v$1@dont-email.me> <vlblqj$harb$1@dont-email.me>
 <lttopaFoh2cU8@mid.individual.net> <vle8uk$12sii$2@dont-email.me>
 <c686fb74-4fac-0809-7005-417c76ee0e3b@example.net>
 <nbReP.633803$oR74.271654@fx16.iad> <NnVeP.44028$vfee.11890@fx45.iad>
 <vo6ubb$3ue2q$2@dont-email.me>
 <RhOdnY5Kb8vulDr6nZ2dnZfqnPudnZ2d@earthlink.com>
 <vo7lp6$25uo$2@dont-email.me>
 <655acbf6-05e5-69ff-8a44-9f7075aafa2e@example.net>
 <ddNpP.567620$iNI.244105@fx14.iad> <m0pqs3ForauU2@mid.individual.net>
 <g9qcnUmy1pxdrTX6nZ2dnZfqnPqdnZ2d@earthlink.com>
 <m0r59mFrbnU1@mid.individual.net> <yn0qP.587031$iNI.359829@fx14.iad>
 <VtWdnaJY5fz99zT6nZ2dnZfqnPudnZ2d@earthlink.com>
 <20250210093054.00001375@gmail.com> <vofgo6$1p8fn$1@dont-email.me>
 <KwSdnd_yRPwhvjH6nZ2dnZfqnPidnZ2d@earthlink.com>
 <20250212081704.00003ce1@gmail.com>
 <slrnvqq09r.38buj.candycanearter07@candydeb.host.invalid>
From: "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net>
Organization: WokieSux
Date: Wed, 12 Feb 2025 17:09:18 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <slrnvqq09r.38buj.candycanearter07@candydeb.host.invalid>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Message-ID: <DKOcnSWcJP6OgTD6nZ2dnZfqnPqdnZ2d@earthlink.com>
Lines: 33
X-Usenet-Provider: http://www.giganews.com
NNTP-Posting-Host: 99.101.150.97
X-Trace: sv3-JhBh8YWbVJk3lUn+JH3VwvQcdJWdg4BoPZ1q3amYgku+EoFOnpB4iCdvnahp70uP3W2QoZE1xwjJz/O!NehPHJL48vPix3Ek4rZqVL74xLNZ6Bus1FnT0EEDe+DAdiuajLPGK+OcAhEAMNBOyW0JhCQgZZ5b!gGgRg9QGd5SK+usNW2io
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
Bytes: 3748

On 2/12/25 3:20 PM, candycanearter07 wrote:
> John Ames <commodorejohn@gmail.com> wrote at 16:17 this Wednesday (GMT):
>> On Tue, 11 Feb 2025 23:29:43 -0500
>> "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> wrote:
>>
>>> Nothing wrong, or unique, about fixed-size arrays. You don't want
>>> them for some stuff, do want them for other stuff. CAN elim a lot of
>>> range-checking code.
>>
>> Nothing wrong with fixed-size arrays as a general concept, no. Treating
>> the size as *part of the type specification* so that passing ARRAY
>> [1..15] OF CHAR to a function expecting ARRAY [1..10] OF CHAR yields a
>> type mismatch is what's utterly demented; a true Wirth original, that.
>>
>> I have never yet heard a sensible case made for a language where array
>> sizes are known, but no FOR EACH IN (x) construct is provided. Doing it
>> C's way at least offers you flexibility and performance in exchange for
>> the risk of shooting yourself in the foot; offering a way to iterate
>> transparently across arrays of arbitrary size at least gives you safety
>> and convenience in exchange for the performance penalty of bounds-
>> checking. Wirth's approach offers the worst of both worlds, for no
>> material gain whatsoever - absolutely bonkers.
> 
> 
> If you really need to, you can also pass by pointer?


   In PASCAL ? Sure.

   As for including size info in arrays ... makes good
   sense to me. EZ to know what you're dealing with.
   Liked the old short-strings in Turbo - the first byte
   was the string length.