Thanks Daniel, that clarifies things a bit. It's how I thought it might
work, but I wasn't sure it actually did. After all, a compiler might
optimise and unroll such extends into longhand anyway, but I take it the RB
compiler doesn't (can't) assume you'd want that to happen?
Ronald Vogelaar
http://www.rovosoft.com
----- Original Message -----
From: "Daniel Stenning" <[EMAIL PROTECTED]>
I am definitely NOT a C proponent btw :)
Concering extends - it will depend on whether you are using the extends in
a
very large loop or just once. Every method or function call requires stack
operations which take a number of processor cycles. The more arguments on
the function the more has to be "pushed" on to the stack and then "popped"
off. Every app ever written is using the stack all the time ( every time a
function or method is called ) but if one is using an extension function
to
replace a line of code it could be quite expensive compared to just
writing
out the same line of code "longhand".
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
