Safe code as an I/O requirement

aberba via Digitalmars-d digitalmars-d at puremagic.com
Sun May 28 09:58:53 PDT 2017


https://lwn.net/Articles/708196/

 From the look of things and feedbacks from several security 
analysts and system developers, [exposed] I/O needs to be memory 
safe.

GStreamer multimedia library developed in C has safety issues 
[see article]. What would its safety be if it was written in D 
(along with its plugins)?


More information about the Digitalmars-d mailing list