i'm working lexisnexis visualfiles, scripting language doesn't allow descriptive variable names - allows "temporary fields" , "local fields" named tf01, tf02 or lf01, lf02 etc. other data comes "entities" descriptive name of entity "selectedentity.en01" instance.
this horribly difficult maintain, lot of i'm editing wasn't commented when written. particularly, if find need use new variable after writing block of code, find i'm trying invent variable numbers i'm reasonably haven't been used anywhere else. have suggestions how make code readable , maintainable, short of commenting each , every single line manually?
edit: not ecl, scripting language visualfiles. there no resources can find online, reference file comes software. sort of code i'm trying decipher:
[&assign lf12=""] [&assign lf13=""] [&assign lf10=aran_aafoo.en02] [&assign lf11=aran_aafoo.en56] [&assign lf12=aran_aafoo.abar_aran.det03] [&assign lf13=aran_aafoo.abar_aran.det02] [&if lf12<> "this" &and lf12 <> "that"] [&if lf13=""] [&assign lf13="something"] [&else] [&assign lf13=lf13] [&endif] [&if det12="yes"] **priority [&assign lf35="top"] [&assign lf36="abnormal"] [&else] [&assign lf35="bottom"] [&assign lf36="normal"] [&endif] any variable can type, i'm looking system me keep organised , keep track of i'm writing - if "comment everything" solution that's fine too.
unfortunately there isn't easy way this. maybe initialise lf fields @ top of script comment next each lf relates to. it's worth remembering lf fields local script\document , tf duration of session i.e. go between scripts. it's worth trying use lf fields possible. can right click on field, such det12 1 on example , give field label.
it's pretty messy , without prior knowledge of db fields , commenting can nightmare maintain else's work.
Comments
Post a Comment