News for hackers. Stuff that matters.
Re:The Safe C Library (2009) by durandal1 on Wednesday April 12, 2017 @08:44PM (#14103106)
In how many "safe" languages can you write a complete shipping application without calling into libraries and/or kernels written in C?
Re:The Safe C Library (2009) by thesuperbigfrog on Wednesday April 12, 2017 @11:10PM (#14103839)
It depends on what platform you are targeting, but as far as safe languages go, it is hard to beat Ada: https://en.wikipedia.org/wiki/Ada_(programming_language)

Although Rust shows a lot of promise, Ada has a proven track record of use in safety critical applications such as avionics and railways.

Re:The Safe C Library (2009) by nickpsecurity on Wednesday April 12, 2017 @09:00PM (#14103186)
Is C being in at some point even relevant? There's plenty of safer languages thst can fo that. There's also containers, OS's, and embedded runtimes for some. The first, business mainframe was even programmed in an early one. It's even still on market although less desirable today. And C itself has automated toolimg available like SAFEcode that can make it safer with one team doing that for FreeBSD.

So you can make the C safe or get rid of it. However much work you want to put in.

Re:The Safe C Library (2009) by pcwalton on Wednesday April 12, 2017 @11:15PM (#14103857)
You can make the same argument for assembler.
Re:The Safe C Library (2009) by geofft on Wednesday April 12, 2017 @08:52PM (#14103144)
Today? Zero, probably.

Five years from now? Probably a number of them. You've been able to write in Go with no standard library for years. There's a project to avoid it in Rust. There are lots of active kernel development projects. Do you want your software to continue to be written in C with a kernel and standard library in safe languages?

And why does it matter to you to avoid improving your code until it's possible to run on an all-safe stack? It is as if it is 1990, and you are asking, why should I license my code as free software? How much can I run on a free C library and a free kernel?

Re:The Safe C Library (2009) by steveklabnik on Wednesday April 12, 2017 @09:03PM (#14103200)
You don't need a project to do it with Rust, you just need a !#[no_std] marker.
Re:The Safe C Library (2009) by steveklabnik on Wednesday April 12, 2017 @09:02PM (#14103195)
You can do so with Rust, and there's a number of them, from toy POCs to much more serious projects.
Re:The Safe C Library (2009) by pjmlp on Thursday April 13, 2017 @12:27AM (#14104162)
Lots of them, like any Modula descendent.

C only became relevant outside UNIX around the late 90's.

Re:The Safe C Library (2009) by khedoros1 on Thursday April 13, 2017 @01:18AM (#14104334)
That doesn't sound right. A ton of DOS software in the late 80s and early 90s was written in C.
Re:The Safe C Library (2009) by pjmlp on Thursday April 13, 2017 @09:07AM (#14106462)
Not at all.

MS-DOS was written in Assembly, just like any application where performance mattered.

CRUD applications were mostly written in an xBase dialect, with Clipper being the prominent one.

Turbo Pascal, Turbo C, Turbo C++, Turbo Basic, Quick Basic, Quick C, Quick Pascal.... All of them had plenty of users.

I own MS-DOS system programming books, with examples in Assembly, Pascal, Basic and C for both Microsoft and Borland variants.

Re:The Safe C Library (2009) by otterley on Thursday April 13, 2017 @03:13AM (#14104801)
Are you thinking of Pascal, maybe? I thought that was the language of choice for DOS application development (and 8086 assembly, of course).
Re:The Safe C Library (2009) by khedoros1 on Thursday April 13, 2017 @12:56PM (#14108730)
I'm thinking of games, really. The ones I'm most familiar with had certain performance-critical parts written in assembly, with the bulk of the connective code written in C. I suppose it depends on the definition of "written in C".
Re:The Safe C Library (2009) by pjmlp on Saturday April 15, 2017 @08:25AM (#14120457)
So not C at all, that was a common practice in Basic and Pascal as well.

Those languages were the "Unity" of the 80 and 90's.

Real games were 100% Assembly.

This only started to change with the adoption of Watcom C, as it could generate relatively good code and use a DOS 32 bit Extender.

Re:The Safe C Library (2009) by AstralStorm on Thursday April 13, 2017 @07:04AM (#14105793)
That and advanced variants of BASIC such as GWBasic and QBasic.

There is a good reason why Visual Basic is still alive.