News for hackers. Stuff that matters.

A comment on C String Creation.

Re:C String Creation by jws on Thursday February 11, 2016 @05:35PM (#11083875)
Good news in the article, apparently asprintf is scheduled for the next POSIX standard. I wonder how one sees what is in the next POSIX standard, it would inform my choices of what I use. I'll use something that works on all my platforms if it is headed to a standard, but usually not if it may head to oblivion.

Also open_memstream is POSIX 2008, now if it would just get into OS X…

[ Parent | on HN ]
Re:C String Creation by generic_user on Thursday February 11, 2016 @11:11PM (#11085242)
These functions are proposed for the next C standard. They are in part 2 of the bounds checking interface. The relevant proposal is n1337 'dynamic allocation functions'

  asprintf() 
  aswprintf()
  vaswprintf()
  fmemopen() 
  open_memstream() 
  open_wmemstream()
[ Parent | on HN ]
Re:C String Creation by audidude on Thursday February 11, 2016 @07:04PM (#11084375)
If you want this today on all (C89) platforms, GLib ships an embedded copy of gnulib and runs virtually everywhere.
[ Parent | on HN ]
Re:C String Creation by sortie on Friday February 12, 2016 @02:40AM (#11085816)
gnulib is atrocious beyond belief though. I hear GLib tends to abort your process on OOM, though I haven't done my research on this library, so I would be careful using these to develop reliable software.
[ Parent | on HN ]