The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
i) Can you tell me the difference between a Compiler and an Interpreter language and why it might be an advantage to translate a programme using a compiler rather than a interpreter?
i) Compare the operation of the compiler with that of an interpreter
i) Identify and justify a situation where a compiler might be preferred to an interpreter
i)Identify and justify a situation where a interpreter might be preferred to an compiler
i)Is source code where something is read from and object code part of the code that tells you what to do to a certain 'thing'. If not, what are Source and Object codes
My computing teacher spends more time harassing year nines and drinking coffee than he does teaching us so I need some help please, Ic, Ali, Blue Eagle, anyone?
[S]Posted this in General too but I know some of the top brass dont venture there often.
i) Compare the operation of the compiler with that of an interpreter
i) Identify and justify a situation where a compiler might be preferred to an interpreter
i)Identify and justify a situation where a interpreter might be preferred to an compiler
i)Is source code where something is read from and object code part of the code that tells you what to do to a certain 'thing'. If not, what are Source and Object codes
My computing teacher spends more time harassing year nines and drinking coffee than he does teaching us so I need some help please, Ic, Ali, Blue Eagle, anyone?
[S]Posted this in General too but I know some of the top brass dont venture there often.
Page:
i) Can you tell me the difference between a Compiler and an Interpreter language and why it might be an advantage to translate a programme using a compiler rather than a interpreter?
i) Compare the operation of the compiler with that of an interpreter
i) Identify and justify a situation where a compiler might be preferred to an interpreter
i)Identify and justify a situation where a interpreter might be preferred to an compiler
i)Is source code where something is read from and object code part of the code that tells you what to do to a certain 'thing'. If not, what are Source and Object codes
My computing teacher spends more time harassing year nines and drinking coffee than he does teaching us so I need some help please, Ic, Ali, Blue Eagle, anyone?
[S]Posted this in General too but I know some of the top brass dont venture there often.
i) Compare the operation of the compiler with that of an interpreter
i) Identify and justify a situation where a compiler might be preferred to an interpreter
i)Identify and justify a situation where a interpreter might be preferred to an compiler
i)Is source code where something is read from and object code part of the code that tells you what to do to a certain 'thing'. If not, what are Source and Object codes
My computing teacher spends more time harassing year nines and drinking coffee than he does teaching us so I need some help please, Ic, Ali, Blue Eagle, anyone?
[S]Posted this in General too but I know some of the top brass dont venture there often.
Paradox: wrote:
> i) Can you tell me the difference between a Compiler and an
> Interpreter language
"Compiled" code is basically code that is "processed" into a binary executable, which then can be run/executed whenever you want to use it.
An interpreter language is where the code is "executed" line by line, it interprets and process's each line of code and runs it.
> and why it might be an advantage to translate a
> programme using a compiler rather than a interpreter?
Advantages of a compiler: -
• Once compiled, the program can be ran as much as you want, it doesn't need to be "re-compiled" each time you execute it.
• Any errors can be found in the program during compilation, i.e you don't have to wait until you run the code to find the error.
Advantages of an interpreter: -
• Much faster to run, you can run the program without having to wait until its finished compiling the whole source. It reads each line then "interprets" it
Disadvantages of an interpreter: -
• You won't encounter errors until that line of code is executed. Meaning you could miss out on unfixed bugs in your program.
• By reading it line by line, each time you run the code, it's being "line-compiled" every time.
i) Compare the operation of the compiler with that of an interpreter
Compiler: -
• Compiles code into a binary executable, checks for errors
Interpreter: -
• Executes code line by line.
i) Identify and justify a situation where a compiler might be
preferred to an interpreter
When compiling an operating system, you want to find the error straight away without having to mess around with "looking" for the error. I.e the compiler will throw an error when it encounters one during compilation.
i)Identify and justify a situation where a interpreter might be
preferred to an compiler
When compiling small programs for debugging, especially useful when you are looking for bugs in programs, I.e when you execute a certain command, you want to see if it runs smoothly.
I'm not sure about your last question, we haven't done that yet.
You doing Tods Tyres?
> i) Can you tell me the difference between a Compiler and an
> Interpreter language
"Compiled" code is basically code that is "processed" into a binary executable, which then can be run/executed whenever you want to use it.
An interpreter language is where the code is "executed" line by line, it interprets and process's each line of code and runs it.
> and why it might be an advantage to translate a
> programme using a compiler rather than a interpreter?
Advantages of a compiler: -
• Once compiled, the program can be ran as much as you want, it doesn't need to be "re-compiled" each time you execute it.
• Any errors can be found in the program during compilation, i.e you don't have to wait until you run the code to find the error.
Advantages of an interpreter: -
• Much faster to run, you can run the program without having to wait until its finished compiling the whole source. It reads each line then "interprets" it
Disadvantages of an interpreter: -
• You won't encounter errors until that line of code is executed. Meaning you could miss out on unfixed bugs in your program.
• By reading it line by line, each time you run the code, it's being "line-compiled" every time.
i) Compare the operation of the compiler with that of an interpreter
Compiler: -
• Compiles code into a binary executable, checks for errors
Interpreter: -
• Executes code line by line.
i) Identify and justify a situation where a compiler might be
preferred to an interpreter
When compiling an operating system, you want to find the error straight away without having to mess around with "looking" for the error. I.e the compiler will throw an error when it encounters one during compilation.
i)Identify and justify a situation where a interpreter might be
preferred to an compiler
When compiling small programs for debugging, especially useful when you are looking for bugs in programs, I.e when you execute a certain command, you want to see if it runs smoothly.
I'm not sure about your last question, we haven't done that yet.
You doing Tods Tyres?
I've finished my Tods Tyres, I found it easy.
My programming teacher sucks
My programming teacher sucks
Tod's tyres? Pfft. Pisch-easy.
Created it in Access and it's sweeeet.
Created it in Access and it's sweeeet.
FYI
Source code is what you write, and then feed into an interpreter or a compiler.
Object code is what the computer understands and executes, i.e. its what the interpreter or compiler generates from your source code.
Source code is what you write, and then feed into an interpreter or a compiler.
Object code is what the computer understands and executes, i.e. its what the interpreter or compiler generates from your source code.
A couple more things - compilers make it easier to distribute your work to other people. You may even only need to distribute the .exe file, depending on the language. Also, if the code is interpreted, you need to distribute your source code, which doesnt do much for your copyright.
BTW, neither helps you to weed out the logic errors in your pgm. A compiler will detect the syntax errors but not your screwed-up logic. I always found interpreted code much easier to debug because its instant to change and try again.
BTW, neither helps you to weed out the logic errors in your pgm. A compiler will detect the syntax errors but not your screwed-up logic. I always found interpreted code much easier to debug because its instant to change and try again.
Thanks doc :-)
2nd year computing coursework is much more interesting (and time consuming) that 1st year. Although when I did my 1st-year coursework we had to code it - couldn't use Access alone.
Uncle Albert wrote:
> 2nd year computing coursework is much more interesting (and time
> consuming) that 1st year. Although when I did my 1st-year coursework
> we had to code it - couldn't use Access alone.
If you're talking about degree level, the difficulty and intensity roughly doubles each year.
> 2nd year computing coursework is much more interesting (and time
> consuming) that 1st year. Although when I did my 1st-year coursework
> we had to code it - couldn't use Access alone.
If you're talking about degree level, the difficulty and intensity roughly doubles each year.
Miserableman wrote:
> Uncle Albert wrote:
> 2nd year computing coursework is much more interesting (and time
> consuming) that 1st year. Although when I did my 1st-year coursework
> we had to code it - couldn't use Access alone.
>
> If you're talking about degree level, the difficulty and intensity
> roughly doubles each year.
I would agree and disagree. It gets harder but because you gradually move up in difficulty the jump isnt as hard, especially if you need amazing in the 1st year. At the moment my degree is getting pretty hetic. Got a group project to finish off which is a Java Battleships game, and also finish off my dissertation on JavaBeans, plus 2 more 2,000 words essay all in just under 2 months.
> Uncle Albert wrote:
> 2nd year computing coursework is much more interesting (and time
> consuming) that 1st year. Although when I did my 1st-year coursework
> we had to code it - couldn't use Access alone.
>
> If you're talking about degree level, the difficulty and intensity
> roughly doubles each year.
I would agree and disagree. It gets harder but because you gradually move up in difficulty the jump isnt as hard, especially if you need amazing in the 1st year. At the moment my degree is getting pretty hetic. Got a group project to finish off which is a Java Battleships game, and also finish off my dissertation on JavaBeans, plus 2 more 2,000 words essay all in just under 2 months.
Page: