From: musiphil@bawi.org   
      
   On 2014-02-14 23:17, Öö Tiib wrote:   
   >   
   > Code that uses Berkeley sockets API directly either does not work (too   
   > naive) or is quite big. One can write very light wrapper indeed but   
   > that forwards all the issues, adds no convenience and so ... is just   
   > bloat.   
      
   Why would it just "not work" or "add no convenience"?   
   I can imagine that a very thin wrapper around the Berkeley sockets API   
   (e.g. a class that encapsulates a socket descriptor) can at least let us   
   write RAII-style code and help a lot with cleanup when an error happens.   
   (I still remember having to resort to multiple goto's just for cleanup   
   when writing a networking program in C... not very pleasant!)   
      
   --   
   Seungbeom Kim   
      
      
         [ See http://www.gotw.ca/resources/clcm.htm for info about ]   
         [ comp.lang.c++.moderated.    First time posters: Do this! ]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)