> ----- Original Message ----- From: "Viktor Szakáts" <harbour...@syenar.hu> > To: "Harbour Project Main Developer List." <harbour@harbour-project.org> > Sent: Wednesday, February 03, 2010 11:53 PM > Subject: Re: [Harbour] Harbour / Clipper Incompatibility Issue: 10 > charvariables with SAVE and REST w/ proof of concept > >> Was thinking a bit more about this... I suppose there are some things in >> Clipper and Harbour that are not compatible.. such as long variable names... >> >> Since this likely won't be changed, as I also prefer long variable names... >> but would would be the best way to do to just keep going ahead with porting >> our old .PRG's to Harbour? > > - Avoid using .mem files. Use .ini files, or .dbf, or serialized variables if > > but, wasn't there compiler compat switch, forceing harbour to use just first > 10 chars of var name? > just to help as fast as possible code porting
We've only discussed it, but it's not possible to solve the problem using a compiler switch. In the past we had a Harbour build-time switch for this though, which could have solved the problem, but this switch got removed as it was not possible to create valid build since long because first 10 chars of many Harbour function names used wasn't unique. IOW it would require to restrict ourselves to crippled 10 chars functions/variables names to keep the codebase compatible with above build-time switch, but practice showed that this rule is impossible to enforce and would pose too much of a limitation. Also, nobody ever tested or needed such builds. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
