Yeah, i gathered that. You have registers to point at stacks, so you automatically know that they arent as fast ;)
Anyway, Now I know what buffer overflows are!!! sweet :) So that would be why you can execute foreign code using it.. Bad design, imho.
Anyway, that post right after marks was when i hadn't seen mark's. and i've just seen it now. And yes, that method looks great :)
strict is more efficient, eh? Sweet.
Oh, and, mark, what's the word on overidden functions/ private members/ properties? I'd like a definite yex/no so i can stop mentioning it in any relevant thread ;()
private members especially, as there are some things you dont wnat messed with. For instance, it seems that in the modules the fields starting with "_" are things you would normally have private. Is this functional or is it just to make it harder to guess or something? However, overridden functions would be very handy because you can't use the determine type trick on builin-types, to make a function that responds to totally different data types. Having functions with different numbers of parameters isnt as useful, and more confusing, Properties are useful because they replace the theory of making a bunch of set/get functions for all your fields (so later on you can make additional code execute when something is set/gotten, or you can apply some procesing, whatever). Using the old system people would often create massive lists of set/get functions so later on you could add code while keeping back-compatability. Properties changes that. You access fields like they should be. As variables. When you want to make a property for a field, you make the actual field private, change its name a bit, create a property with get/set methods inside. Then, you maintain back compatability and field-syntax.
Anyway, Now I know what buffer overflows are!!! sweet :) So that would be why you can execute foreign code using it.. Bad design, imho.
Anyway, that post right after marks was when i hadn't seen mark's. and i've just seen it now. And yes, that method looks great :)
strict is more efficient, eh? Sweet.
Oh, and, mark, what's the word on overidden functions/ private members/ properties? I'd like a definite yex/no so i can stop mentioning it in any relevant thread ;()
private members especially, as there are some things you dont wnat messed with. For instance, it seems that in the modules the fields starting with "_" are things you would normally have private. Is this functional or is it just to make it harder to guess or something? However, overridden functions would be very handy because you can't use the determine type trick on builin-types, to make a function that responds to totally different data types. Having functions with different numbers of parameters isnt as useful, and more confusing, Properties are useful because they replace the theory of making a bunch of set/get functions for all your fields (so later on you can make additional code execute when something is set/gotten, or you can apply some procesing, whatever). Using the old system people would often create massive lists of set/get functions so later on you could add code while keeping back-compatability. Properties changes that. You access fields like they should be. As variables. When you want to make a property for a field, you make the actual field private, change its name a bit, create a property with get/set methods inside. Then, you maintain back compatability and field-syntax.