Re:Microcode: the place where hardware and software meet
by nixbun on Sunday March 10, 2013 @11:40AM
(#5352275)
A bit off topic, but I've always wondered why some refer to the language as 'assembler' whereas others call it 'assembly'. I always thought the assembler is the name of the thing that reads in your assembly code and turns it into a machine binary. Is there some historical significance to calling it 'assembler'?
[ Parent
| on HN ]
Re:Microcode: the place where hardware and software meet
by jmilinion on Sunday March 10, 2013 @07:40PM
(#5354097)
I'm not old enough to know but my theory is things in the programming world historically came from the computer architectural world. Computer architecture uses stacks, interrupts (events), and other things in the physical layout of the computer chip. When people were done with the hardware stuff, they created software which has similarities to hardware and thus called them the same. When people then created higher level software from lower level software, they saw similarities there as well and went from there.
Re:Microcode: the place where hardware and software meet
by jonsen on Sunday March 10, 2013 @12:40PM
(#5352485)
Calling the language assembler might be considered potentially confusing and ambiguous, since this is also the name of the utility program that translates assembly language statements into machine code. However, this usage has been common among professionals and in the literature for decades.:
http://en.wikipedia.org/wiki/Assembler_(computing)#Assembler