So what is the story about __fastcall? I just know that Borland uses it in all functions when something is returned.
So what is the story about __fastcall? I just know that Borland uses it in all functions when something is returned.
if that's true then why not just put every thing into the register? (Ofcource there is a point doing that. I would just like to what what that point is.)
Well english isn't my first language, (it's instead a useless language called danish which only 5 milion people speak!!) so if you think my grammar SUCKS (it does by the way) than you're more then welcome to correct me.
Hell I might even learn something
Because registers are quite small. Sixteen to thirty two bits a pop, times maybe four or six that you can access, depending on CPU type.
The stack, OTOH, can hold tons of data.
But isn't it then kind of dangerus when Borland 6.0 uses __fastcall in all it's funktions?
Well english isn't my first language, (it's instead a useless language called danish which only 5 milion people speak!!) so if you think my grammar SUCKS (it does by the way) than you're more then welcome to correct me.
Hell I might even learn something
It would be tricky to implement, but not really dangerous if you knew what you were doing. And for 32 bit data types (pointers) it is faster. Not MUCH faster, but every little bit helps.
So it's them all or none of 'em?
Well english isn't my first language, (it's instead a useless language called danish which only 5 milion people speak!!) so if you think my grammar SUCKS (it does by the way) than you're more then welcome to correct me.
Hell I might even learn something
