On Tue, 11 Nov 2008, Szak�ts Viktor wrote: Hi Viktor,
> It's a Clipper '87 heritage and much slower than > LOCAL/STATIC, it can make programs very difficult Have you checked it? You'll be very surprised if you will make some tests. In tests/speedtst.prg tests 1-15 checks the speed of local, static, public, privates and fields. Do you see noticeable speed difference between first four variable types? > to understand/read/modify/maintain, even more so in > MT programs, and they both can be replaced by better > alternatives since a very long time. What is the alternative for variables in macros? > Probably a compiler switch could be the solution, > which would tell it to trim all such names. The > default of this switch is something we can decide. It will help only for variables used explicitly in source code but will not for macros. It will have to be also runtime HVM switch. > [ Unless there is any other obvious/existing solution > for the problem of course. Heavily editing RL sources > doesn't count. ] I do not know the RL tool and it's internal format used in .frm but for .mem files we can introduce new format which will allow to store memvars with unlimited variable name size. best regards, Przemek _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
