Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c > #139146

Re: Methodologies for C programming

Subject Re: Methodologies for C programming
Newsgroups comp.lang.c
References <376535a0-079d-4e93-811b-8fdcfabd6cb2@googlegroups.com> <q03752$mg$1@dont-email.me>
From Richard Damon <Richard@Damon-Family.org>
Message-ID <KKcVD.42471$qC3.18211@fx28.iad> (permalink)
Organization Forte - www.forteinc.com
Date 2018-12-27 17:54 -0500

Show all headers | View raw


On 12/27/18 1:54 PM, jacobnavia wrote:
> Le 07/12/2018 à 14:15, Thiago Adams a écrit :
>> In C we need to build your own data types. Comparing with C++
>> for instance, we have parametrized data types like vector and map
>> and other read-to-use types like string.
>>
>> Therefore, to avoid doing everything again and again we need to
>> think in modularization and reuse. Using C++ someone else is in
>> charge for testing the STL containers. Doing you own data types
>> we need to make sure everything is working and unit tests also
>> become very important.
> 
> To avoid that, I designed and developed a prototype STL for C, offering
> very similar capabilities and faster performance.
> 
> The C standards committee rejected the proposal saying that C++ has done
> that already, and any development of an STL in C is out of the question.
> 
> I have tried to promote the library in this group (used mainly by C++
> people)  to no avail.
> 
> What is the CCL?
> 
> It provides
> o Hash tables
> o Flxible vectors
> o Trees
> o String vectors
> o lists (single/double linked)
> 
> Parametized types are provides through macros.
> Allocation can be replace by your own allocator.
> 
> It provides also iterators, you can be notified of changes in anyy
> container, provides read only containers, and a LONG "etc"
> 
> But it has an enormous drawback:
> 
> It is written in standard C (1999), and as everyone in this group has
> told me, C is a dead language, goto C++
> 

Jacob, I have looked at and tried to use your library, but it comes off
feeling like C++ code that has been ported to C, not as C code, which I
think is part of the issue that the Standards Committee saw. If
anything, I think you set your sites on implementing too much of the
STL, and ended up with something that just doesn't feel like C.

In an application that I would be tempted to use it, I would with just a
bit of push go all the way to implementing in C++.

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Methodologies for C programming Thiago Adams <thiago.adams@gmail.com> - 2018-12-07 05:15 -0800
  Re: Methodologies for C programming Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-12-07 05:38 -0800
    Re: Methodologies for C programming Thiago Adams <thiago.adams@gmail.com> - 2018-12-07 07:57 -0800
      Re: Methodologies for C programming David Brown <david.brown@hesbynett.no> - 2018-12-07 18:05 +0100
  Re: Methodologies for C programming Thiago Adams <thiago.adams@gmail.com> - 2018-12-07 08:08 -0800
  Re: Methodologies for C programming William Ahern <william@25thandClement.com> - 2018-12-07 10:08 -0800
    Re: Methodologies for C programming Thiago Adams <thiago.adams@gmail.com> - 2018-12-07 10:23 -0800
  Re: Methodologies for C programming Wouter Verhelst <w@uter.be> - 2018-12-07 22:04 +0100
  Re: Methodologies for C programming Ian Collins <ian-news@hotmail.com> - 2018-12-08 10:46 +1300
    Re: Methodologies for C programming Thiago Adams <thiago.adams@gmail.com> - 2018-12-08 02:27 -0800
      Re: Methodologies for C programming Thiago Adams <thiago.adams@gmail.com> - 2018-12-08 10:35 -0800
        Re: Methodologies for C programming Jorgen Grahn <grahn+nntp@snipabacken.se> - 2018-12-09 08:22 +0000
  Re: Methodologies for C programming fir <profesor.fir@gmail.com> - 2018-12-09 14:40 -0800
  Re: Methodologies for C programming "Pascal J. Bourguignon" <pjb@informatimago.com> - 2018-12-27 13:17 +0100
    Re: Methodologies for C programming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2018-12-27 08:12 -0500
    Re: Methodologies for C programming Thiago Adams <thiago.adams@gmail.com> - 2018-12-27 07:54 -0800
      Re: Methodologies for C programming Richard Damon <Richard@Damon-Family.org> - 2018-12-27 11:32 -0500
      Re: Methodologies for C programming fir <profesor.fir@gmail.com> - 2018-12-27 09:22 -0800
  Re: Methodologies for C programming jacobnavia <jacob@jacob.remcomp.fr> - 2018-12-27 19:54 +0100
    Re: Methodologies for C programming Richard Damon <Richard@Damon-Family.org> - 2018-12-27 17:54 -0500
      Re: Methodologies for C programming fir <profesor.fir@gmail.com> - 2018-12-27 16:24 -0800
        Re: Methodologies for C programming Chad <cdalten@gmail.com> - 2018-12-27 17:57 -0800
        Re: Methodologies for C programming Chad <cdalten@gmail.com> - 2018-12-27 17:58 -0800
          Re: Methodologies for C programming rbowman <bowman@montana.com> - 2018-12-27 21:34 -0700
            Re: Methodologies for C programming Keith Thompson <kst-u@mib.org> - 2018-12-27 21:27 -0800
              Re: Methodologies for C programming rbowman <bowman@montana.com> - 2018-12-28 08:30 -0700
                Re: Methodologies for C programming Keith Thompson <kst-u@mib.org> - 2018-12-28 12:15 -0800
                Re: Methodologies for C programming rbowman <bowman@montana.com> - 2018-12-28 20:42 -0700
                Re: Methodologies for C programming Tim Rentsch <txr@alumni.caltech.edu> - 2018-12-29 09:26 -0800
                Re: Methodologies for C programming rbowman <bowman@montana.com> - 2018-12-29 13:50 -0700
  Re: Methodologies for C programming luser droog <luser.droog@gmail.com> - 2018-12-30 12:39 -0800
    Re: Methodologies for C programming fir <profesor.fir@gmail.com> - 2018-12-30 14:00 -0800
      Re: Methodologies for C programming fir <profesor.fir@gmail.com> - 2018-12-30 14:18 -0800
    Re: Methodologies for C programming rbowman <bowman@montana.com> - 2018-12-30 16:48 -0700
      Re: Methodologies for C programming luser droog <luser.droog@gmail.com> - 2018-12-31 00:06 -0800
        Re: Methodologies for C programming fir <profesor.fir@gmail.com> - 2018-12-31 02:34 -0800
        Re: Methodologies for C programming Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-12-31 05:13 -0800
        Re: Methodologies for C programming rbowman <bowman@montana.com> - 2018-12-31 12:44 -0700
      Re: Methodologies for C programming Tim Rentsch <txr@alumni.caltech.edu> - 2019-01-01 16:01 -0800
      Re: Methodologies for C programming Tim Rentsch <txr@alumni.caltech.edu> - 2019-01-01 16:23 -0800
    Re: Methodologies for C programming Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-12-31 05:08 -0800
      Re: Methodologies for C programming Ike Naar <ike@iceland.freeshell.org> - 2018-12-31 17:32 +0000
        Re: Methodologies for C programming Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-12-31 14:13 -0800
  Re: Methodologies for C programming Thiago Adams <thiago.adams@gmail.com> - 2019-01-02 02:48 -0800

csiph-web