Hummm, I am not sure this would work without doing some weird stuff. Yes, SysFile has two implementations, but it also has two different make files (Windows and *nix). I don't think we currently have any conditional products for the Windows or *nix versions of ooRexx (considered separately). For *nix this would require that the make utility could process conditional directives, and it does not have the capacity to do so (the Windows nmake has this facility and it is the one thing about the Windows development environment I really miss).
So the question becomes how do we figure out at compile/packaging time which version of rxapi to build/package? I don't see how it could be done except by the configure script and I question if that is the correct place to implement this functionality. It might be the right place, but I am just not sure. David Ashley On 02/21/2011 11:22 AM, Mark Miesfeld wrote: > On Mon, Feb 21, 2011 at 6:42 AM, Rick McGuire<object.r...@gmail.com> wrote: > >> One approach we've used a lot is to have the build for a particular >> platform determine which code gets linked in to an executable. For >> example, the SysFile class has two distinct implementations, and the >> makefiles determine which one gets compiled and linked. For the rxapi >> executable, we have the same thing (one Windows, one *ix). This can >> certainly be extended to as many levels as we need to configure the >> required platform behavior. > This is the way we should go with this I believe. It seems more in > line with what we are doing already in the interpreter. > > -- > Mark Miesfeld > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
