Re:Dennis Ritchie's first C compiler on Github
by mseepgood on Wednesday May 22, 2013 @12:32AM
(#5748894)
> (Spoiler - We start with BCPL, then Move to B - it's left as an exercise to determine how we originally compiled BCPL)
The first version of Go started with B: http://code.google.com/p/go/source/detail?r=f6182e5abf5e
The second revision was converted to C: http://code.google.com/p/go/source/detail?name=f6182e5abf5e&...
The third to Draft-Proposed ANSI C: http://code.google.com/p/go/source/detail?name=f6182e5abf5e&...
And the fourth to ANSI C: http://code.google.com/p/go/source/detail?name=f6182e5abf5e&...
Re:Dennis Ritchie's first C compiler on Github
by chubot on Wednesday May 22, 2013 @02:41AM
(#5749259)
Uh these commits seem interesting, but I don't quite understand the context. What's macho and what is its relation to go? Are the dates way off or is it an import of older history?
Re:Dennis Ritchie's first C compiler on Github
by glurgh on Wednesday May 22, 2013 @03:38AM
(#5749389)
Your leg is being pulled, a little. Mach-o is the mach object file format, Brian Kernighan's C 'hello world' program is being used as source for, I think, a test. It's checked into the go tree with version history all the way back to its primordial source.
Re:Dennis Ritchie's first C compiler on Github
by lifthrasiir on Wednesday May 22, 2013 @12:45AM
(#5748931)
They definitely messed up with a conversion from Subversion to Mercurial. ;)
Re:Dennis Ritchie's first C compiler on Github
by hkmurakami on Tuesday May 21, 2013 @11:51PM
(#5748779)
coupled with user:rmrfrmrf's pseudo-religious post praising the code, I read the second url as "christ" :P
Oh how our minds play tricks on us!
http://cm.bell-labs.com/cm/cs/who/dmr/primevalC.html
Which led me to here:
http://cm.bell-labs.com/cm/cs/who/dmr/chist.html
Where, if you take the time, you will find a wonderful story, upon completing, you will probably know more about the early embryonic history of C then 95% of your peers.
(Spoiler - We start with BCPL, then Move to B - it's left as an exercise to determine how we originally compiled BCPL)