The way I understand this thing is that when you use a simple variable (A= 16) what is stored in the object code is an offset value into the descriptor table where the value of A is stored. If you use an EQU A to 16 then what is stored in the object code is 16. When the program is executed the interpreter does not have to look the value of A up in the descriptor table because the value is right in the object code and thus the program executes faster.
That's what I was taught, long, long ago. :-) Tom Dodds [EMAIL PROTECTED] 708-234-9608 Office 630-235-2975 Cell -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kevin King Sent: Saturday, November 18, 2006 1:06 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] [UV] Question about EQU David, I am interested in your opinions as to why, given that equates are compile time constructs, would have any impact at all on execution speed. Understand, I am not contesting your premise, but rather would simply like more explanation to understand your perspective. -Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com ** Check out scheduled Connect! training courses at http://www.PrecisOnline.com/train.html. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
