[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Looping through an array with FOR EACH


Il 15/01/26 18:55, Brian G ha scritto:
I think here we have have Ben step in, because what you are all stating is that 'for each' is a totally unreliable way of for instance listing a newly sorted array of strings... even the hint of a 'maybe not work'  in a production environment is not acceptable on any level. I just don't believe for simple arrays that Ben would allow such a bug/ instability to persist as part of such an amazing work!

If this is on any level true, perhaps this construct should be removed from the language it is therefore a useless construct.
No body should be afraid to use a tool as intended.


Dear Brian,

Yes, I would really appreciate it if Benoit would say something about this.
But it doesn't seem as dramatic as you're making it out to be.
There are constructs better suited than others to do a given thing, and constructs better suited to do something else. Now, I speak as someone who's very ignorant on the subject, but I would use FOR EACH to find all occurrences, knowing that the construct will return them all.
But if I want to know exactly where the occurrences are, then...
Where do you find this reasoning flawed?
As far as I know, C doesn't support For Each.

With Best Regards
Gianluigi


Follow-Ups:
Re: Looping through an array with FOR EACHBrian G <brian@xxxxxxxxxxxxxxxx>
Re: Looping through an array with FOR EACHBenoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx>
References:
Looping through an array with FOR EACHGianluigi <gradobag@xxxxxxxxxxx>
Re: Looping through an array with FOR EACHBB <adamnt42@xxxxxxxxx>
Re: Looping through an array with FOR EACHGianluigi <gradobag@xxxxxxxxxxx>
Re: Looping through an array with FOR EACHBrian G <brian@xxxxxxxxxxxxxxxx>