A
andrew.may
Guest
The compilation is a side-product of the structure. All our legacy code had a flat directory structure & so /src/*.p compiles to /bin/*.r All our new code (procedural or class-based) goes into sensibly named subfolders. e.g. /src/mycompany/myproject/mymodule/myproc.p and /src/mycompany/myproject/mymodule/MyClass.cls These would compile into... /bin/mycompany/myproject/mymodule/myproc.r /bin/mycompany/myproject/mymodule/MyClass.r To use this in code: run mycompany/myproject/mymodule/myproc.p. using mycompany.myproject.mymodule.*. def var o as MyClass. o = new MyClass(). It does make the procedural stuff more wordy (would be nice if we had a "using" equivalent for .p's), but the unambiguity & descriptiveness of the namespaces makes up for it in our opinion. (N.B. we've got a 3-letter company name, if you have a longer one, consider a good abbreviation instead.) e.g. run bcp/backoffice/orderprocessing/importXML.p is more clear than "run importXML.p"
Continue reading...
Continue reading...