Start of a compiler/dependency tool
Version 1 will handle setting up git projects into pick. This will handle primarily handle setting up the q-pointers for the different platforms.
D3 - Create dict, setup Q pointer. Q pointer to root directory jBASE - Create F pointer. Root is dict. Universe - Create F pointer - Universe has a weird format for multiple data sections. Unidata - Unknown OpenQM - Believe it supports both D3 and Universe syntax
Also it would be nice to recognize the platform automatically.
Right now the make program will prompt for where the gitlab project is at and figure everything out from there.
General idea is to come up with some concepts and then tools to handle including modules that are independent to your project.
As an example lets say you want to use the WOBJ library with a new tool you are making. Instead of relying on a global WOBJ library that may be updated and break your tool you can include WOBJ directly into your project.
As a basic overview
- Seperate BP file for your project. It is named for your project. Lets say MVDEMOBP. bp file would be MVDEMOBP.BP
All code you make should be prefixed with MVDEMOBP.
Now, when you want to include WOBJ into your project, a sub data section is created under MVDEMOBP file MVDEMOBPBP,WOBJ.BP
All code would then be renamed MVDEMOBP. All code doing a CALL WOBJ would be re-written to CALL MVDEMOBP.WOBJ.
At compile time you now have your own version of WOBJ and never have to be worried about another version.
Other items to think about
- tmp files
- commons
- includes
The goal here is to duplicate the package concepts code such as .net, node, and javascript do in which they can include all dependencies directly into their project.