Re:Merging In The GNU D Language Compiler To GCC
by hasenj on Saturday October 08, 2011 @11:11AM
(#3088078)
Interesting, I didn't know there was multi-core even back then.
But still, at least, they weren't as common place as they are now.
Re:Merging In The GNU D Language Compiler To GCC
by sambeau on Saturday October 08, 2011 @10:51AM
(#3088036)
"Personally I see Go as a better C, nothing more."
Which is a good thing, right?
Re:Merging In The GNU D Language Compiler To GCC
by pjmlp on Sunday October 09, 2011 @08:33AM
(#3090353)
Sure, we need safer systems languages.
Re:Merging In The GNU D Language Compiler To GCC
by sambeau on Saturday October 08, 2011 @10:53AM
(#3088040)
To be fair, the way Go uses interfaces is new.
Re:Merging In The GNU D Language Compiler To GCC
by he_the_great on Sunday October 09, 2011 @12:00PM
(#3090657)
Nope, not even. SML apparently did so, and probably others.
Re:Merging In The GNU D Language Compiler To GCC
by pjmlp on Sunday October 09, 2011 @08:33AM
(#3090351)
The only thing new about them is that you don't need to write "implements" or something similar.
Re:Merging In The GNU D Language Compiler To GCC
by sambeau on Monday October 10, 2011 @07:07AM
(#3093226)
It is more subtle and powerful than that.
By placing the contract at the use of a type with an interface rather than at the declaration of a type you effectively introduce a form of duck typing to a static language.
You can write an interface for a type long after the type has been declared (or been declared by someone else). Interfaces can be defined and used without having to go back and change existing code. This is very lightweight.
And in 1981 there were already application servers, running in multiprocessor machines using Multics, UNIX and VMS, just to name a few operating systems.
Personally I see Go as a better C, nothing more.