First came machine code using a string of numbers (in binary, octal or hexadecimal) - initially via switches and lights. Second was assemblers using mnemonics such as "add" and "mov". Then, along came high level languages starting with BASIC (on PCs). These were first implemented using translators, converting BASIC to CPU instructions at run time (no EXE). Finally, along came compilers.
Given an initial crude form of assembler or compiler, this can then be used to produce versions with additional facilities.
2007-04-19 00:22:24
·
answer #1
·
answered by ROY L 6
·
0⤊
0⤋
Executables came first. Early development was done directly using machine code which was either entered manually or loaded from punch card. Then someone wrote an assembler in machine code. Then someone wrote a compiler using assembler. Nowadays, people use compilers to write compilers. eg, gcc is used to create new gcc builds.
2007-04-18 23:44:30
·
answer #2
·
answered by Anonymous
·
0⤊
0⤋
Originally, I'd have to say machine code. So yes, simple executables. I've used debug before to write .COM files, and that is sort of hard. The machine code can be used to make .COM files (a simplified executable program), including editors of sorts. Then the editors can be used to create more complex programs, etc.
Actually, we need to think even more primitive. Before compilers and executables, there had to be an operating system, a kernel if you will. Before the kernel, there has to be some bootstrap code (the boot record of a disk). Before the bootstrap code could exist, there had to be BIOS code that could run it.
2007-04-18 22:55:09
·
answer #3
·
answered by Anonymous
·
0⤊
0⤋
I say sturdy for you - super questions. i'm undecided a thank you to respond to them. yet listed right here are some recommendations. An OS starts straight forward as an interface between the hardware and the needs you run. It will become complicated through fact it manages memory, IO units and a brilliant form of purposes working on the comparable time. There are equipment to jot down compilers first you define the way the language works and its syntax, then you definately use those equipment to generate the compiler. yacc is a style of equipment. Interpreted or scripting languages are written slightly in yet differently. making use of a digital device ( a application CPU style) they write to that. Libraries are extra convenient to jot down. they many times address a particular form of activity or initiatives. Like a pics library. Assemblers are based on the cpu the objective. Their mnemonic education set reflects the applications of the CPU they're written for. so which you may desire to comprehend the actual/digital nature of the CPU to create an assembler and to jot down assembly code.
2016-10-03 05:53:36
·
answer #4
·
answered by ? 4
·
0⤊
0⤋
you need a compiler first to make an exe program
2007-04-18 22:47:52
·
answer #5
·
answered by iyiogrenci 6
·
0⤊
0⤋
You can write assembly code which can get executed without getting compiled
2007-04-18 23:36:55
·
answer #6
·
answered by Anonymous
·
0⤊
0⤋
I think firstly the programme is compiled and then it is executed. So, compiler comes first and execution later on.
2007-04-18 22:46:29
·
answer #7
·
answered by Anonymous
·
0⤊
0⤋
scientist compiled their code manually in early times. therefore eecutable program came first which they developped into a compiler!!!!!!!!!
2007-04-18 22:51:58
·
answer #8
·
answered by Aamir Sayid 2
·
2⤊
0⤋
Of course the executable comes first.
A compiler itself is an executable ... Right :)
2007-04-18 22:47:16
·
answer #9
·
answered by StarChaser 5
·
1⤊
0⤋
This a long answer.Get a computer history book. Binary coding and toggle switches came first. Then assembly. But don't take my word for it check out wikepedia
2007-04-18 23:05:50
·
answer #10
·
answered by vulcan 7
·
0⤊
0⤋