I think the approach here would be to have the SysFileSystem class remain the interface between the portable code and the platform, and have its method delegate to a specific pluggable instance.
Rick On Mon, Aug 11, 2008 at 9:59 AM, David Crayford <[EMAIL PROTECTED]> wrote: > ooRexx seems to only handle one type of file system based on the > platform. On my system (z/OS) there are different file systems depending > on the runtime environment. We have a UNIX file system and a traditional > mainframe filesystem using PDS data sets. There is also a UNIX like file > system in CICS. The SysFileSystem class is static, what I really need is > a SysFileSystem factory or different builds depending on where I > want to deploy. Any suggestions? I'm jumping the gun here a bit as I'm > only just starting to code in anger, but it's a concern... > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
