2 ms·

If it were a good C replacement I'd be able to expose an ABI for other language bindings, so that I could write libraries that could be used in many different l

If it were a good C replacement I'd be able to expose an ABI for other language bindings, so that I could write libraries that could be used in many different languages. There is no way to do this in Go. If it were a good C replacement, it would have dynamically linkable libraries so that I could write an extensible server that could be extended with external modules (a la Apache). If it were a good C replacement I'd have direct access to memory so that I could write device drivers.

pjmlp 14y ago
> If it were a good C replacement I'd be able to expose an ABI for other language bindings, so that I could write libraries that could be used in many different languages. There is no way to do this in Go. C ABI is the operating system ABI. If the OS is written in Go, the C ABI becomes irrelevant. > If it were a good C replacement, it would have dynamically linkable libraries so that I could write an extensible server that could be extended with external modules (a la Apache). You can do this with gccgo to some extent already. Eventually this support might come to the standard compiler. This is not a language issue, rather an implementation issue. As anyone with compiler development knowledge can easily explain to you. > If it were a good C replacement I'd have direct access to memory so that I could write device drivers. The Oberon guys did not had any issue with this. Their System package API is quite similar to what Go's unsafe package offers. http://www.inf.ethz.ch/personal/wirth/books/ProjectOberon.pdf http://www.inf.ethz.ch/personal/wirth/books/ProjectOberon.pd... http://e-collection.library.ethz.ch/eserv/eth:26082/eth-26082-02.pdf http://e-collection.library.ethz.ch/eserv/eth:26082/eth-2608...