Dudes. The day we was taught about resolving ambiguity in classes during inheritance (to increase the polymorphism, the single interface many methods jazz) i had about 2 and a half hours sleep, so the lights was barely on but nobody was in and i have practical test coming up relatively soon.
heres some rubbish code to show what i mean :
#include <iostream>
#include <string>
using namespace std;
The method "setstuff" is present in both classes so it does not work properly but borland compilers give a error . The class of "fryup" is inheriting from the class of "baseclass"
"Say you're hanging from a huge cliff at the top of mt. everest and a guy comes along and says he'll save you, and proceeds to throw religious pamphlets at you while simultaniously giving a sermon." - Dustin G
"Say you're hanging from a huge cliff at the top of mt. everest and a guy comes along and says he'll save you, and proceeds to throw religious pamphlets at you while simultaniously giving a sermon." - Dustin G
well, you could compile the same C++ program on 10 different processors, but not assembly... unless of course they all used the same keywords
"Say you're hanging from a huge cliff at the top of mt. everest and a guy comes along and says he'll save you, and proceeds to throw religious pamphlets at you while simultaniously giving a sermon." - Dustin G
Kris thats what i understood, in assembly (well i program a 8088 microcontroller [which is an 8 bit data bus version of the 8086 ] in assembly ) you have to put the memory adress say "mov 0092,AX" move the accumalator contents to mem adress 0x0092. So therefore if the persons computer is using that memory your program will do bugger all. Also if you start doing fancy hardware calls to say a IDE controller its all hardware specific.
Theoretically i could make a program in assembly to work with my GeForce graphics card (3d and stuff), but it would only work with that very chipset and brand.
Oh and a a true compiler translates to machine code and links (if you need it to), a lot of new fangly languages are just interpreters .
when you inherit from this class, and the new class contains a method that is defined as virtual in the baseclass the baseclass's method will be overridden with the inheriters.
Yeah.. you have to use the Standard(forgot the name of what they call the standard ).. anyway. I've been teaching myself C++ for the past month and wow I actually understood that :]