Hi Ken, VFP keeps only one copy of the code around, but will use memory to store the array property just like it does with array variables. Overall I wouldn't expect a big difference in resource huge. Less memory used for code, but more memory used for the object.
You'll experience a reduction in performance albeit a small one for two reasons. Every access to the array now has to first resolve the object reference, which takes some time. More noticeably, though, is replacing direct array function calls with a user defined method. A method call takes some time, because VFP has to create a new stack level. My guess is that the biggest issue is something you haven't mentioned at all: Array properties cannot be passed by reference. So any code that currently passes the array to another function or method has to be rewritten to use the array property. That's either an all or nothing approach by replacing the array in the called method with an object reference, or involves a lot of conditional code based on whether the parameter is an array or an object with the array. -- Christof --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cal4qjhhas4vfuzcpuekcayggf1knjakkg3s+bg8vmgttqnq...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
