Open vincentparrett opened 5 years ago
Probably not. How the tool will know for which platform the package is being installed? As it's source code based it can be compiler for several platforms.
It could look at the dproj and try and figure out what platforms a project targets. I would think that if pre compilation were supported, it would need to be optional, or at least be an ability to turn that off.
Still lots to figure out.
A preprocessor would be useful, but waiting for a response from EMBT, given the many historical precedents, is unfortunately futile.
Now - we could build our own preprocessor as we would seem to be forced. I would suggest that such a processor should simply accept a source file name (say fred.dprp) and an optional destination file name (defaulting to fred.drp) and provide routines to find_nextcharacter, find[and_classify]next_token etc. Processing and output at the user's discretion.
One use for such a scheme would be to exercise proposed language changes such as RSP13777 (which should be easy to do - I'm astonished that EMBT hasn't spent the required half-hour to implement it and claim the accolades for a new feature.)
When a package is installed, and it includes source only (no precompiled binaries), should it be compiled for the platform it's being installed in??
The advantage of doing this is that we can then reference the binaries in the search path, improving project compile times.
The disadvantage is slower package install times. It would also complicate the dependency resolution.