From: Bonita.Montero@gmail.com   
      
   Am 08.10.2025 um 11:53 schrieb Michael S:   
      
   > You don't understand the meaning of the word 'flexible'.   
      
   I understand it, my first solution was o.k. in that sense.   
   The usage is much more simple than in C.   
      
   > The whole point of it is that N is unknown at compile time.   
   >   
   > Formally speaking, flexible array members are not supported in   
   > inferior tongue ...   
      
   As you can see from my first post my solution is much more flexible.   
      
   > However, if I am not mistaken, it works just because implementors are   
   > sane people, rather than because the language itself provides sane   
   > guarantees.   
      
   C is really dangerous in that sense because you've to flip every bit   
   yourself. Better use abstactions you re-use a lot of times. In C there   
   almost no complex data strructures at all; like a vector in C++ or a   
   unordered map because it would be a large effort to  specialize your-   
   self that for every data type. Most C projects stick with simple data   
   structures which are less efficient. The "generic" types in C which   
   work work callbacks like with qsort() really suck since their perfor-   
   mance is better but still not optimal.   
   I think all developers who use C today are either forced to stick   
   with C though their job or are persons which think mostly on the   
   detail level and can't think in abstractions.   
   This is programming like in the beginning of the 90s. But today's   
   machines are capable to handle more complex requirements and these   
   requirements need a more flexible language so that you can handle   
   that with less bugs than in a lanugage where you've to do every   
   detail by yourself.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)