Hello,
today i was asked by a coworker: (a few yerars in company, before programming VB).
Hey, what happens here?
HIST.KONTO = LAGERORT.LIEF
If i use the debugger and select LAGERORT.LIEF as Expression i get: not avail but the code is working!
My answer:
This is a bad joke from ABL!
The full text would be:
HIST.KONTONR = LAGERORT.LIEFERANT
This made sense in the past (bad editors) and for rapid typing text but we still have problem with this feature until today.
Problems:
Fields or if we omit tablename, other fields from other table will be used by this "autosense"
I think this is not Up to Date for a modern language.
I would like to become a -OptionStrict compiler statment to run a check and get an info.
Any comments?
Stefan
Any comments?
http://www.oehive.org/prolint/rules/abbrevtable
Prolint has a rule for abreviated tables and keywords.
Probably not a huge task to extend that for abbreviated field names.
I'd vote for that....but I doubt we'll ever see it outside of Prolint though.
There was functionality to clean up this sort of thing in ProRefactor. I'm sure it wouldn't be hard to use Proparse to force the cleanup.