Advertisement
GStreamer Conference 2013, 22-23 Oct, Edinburgh
GStreamer, Embedded Linux, Android, VoD, Smooth Streaming, DRM, RTSP, HEVC, PulseAudio, OpenGL. Register now to attend.
| |||||||||||||
Big success - so congrats!Big success - so congrats!Posted Oct 4, 2013 10:56 UTC (Fri) by mpr22 (subscriber, #60784)In reply to: Big success - so congrats! by wahern Parent article: 30 years of GNU
Write the majority of your application for POSIX compliance, and you dramatically reduce your workload, including API worries. My application is in C++ and uses terminal graphics (ncursesw). POSIX has virtually nothing to say about C++ (except by implication from saying things about C), and nothing conveniently usable to say about terminal graphics (it specifies termios, but not term{cap,info} or curses). At some point, it's going to acquire audio playback and bitmap graphics - both of which, again, POSIX has nothing to say about.
(Log in to post comments)
Big success - so congrats! Posted Oct 4, 2013 11:17 UTC (Fri) by dlang (✭ supporter ✭, #313) [Link]
but POSIX does say a lot about what the API to the OS looks like. If your program (or it's libraries) written in language FOO stick to using the POSIX system calls, then you are probably in really good shape. If they don't, then you are likely to have problems at some point.
|
|||||||||||||