From: Rick M. <obj...@gm...> - 2009-07-19 22:31:43
|
Hmm, I suspect I couldn't think of a reasonable default at the time. We haven't hit this situation yet, so it might not be a bad idea to let this generate an error if we hit it so that this gets a good examination to decide what the default should be. I do agree we should start changing all of the references to PATH_MAX to the SysFileSystem common value. This should probably just be done in the trunk version unless we find a place where this is really a problem. Rick On Sun, Jul 19, 2009 at 6:20 PM, Jean-Louis Faucher<jfa...@gm...> wrote: > Rick > > I see that MAXIMUM_PATH_LENGTH has no value in last #else. > > This piece of code supports the case where PATH_MAX is not defined. > But we have some files where PATH_MAX is used inconditionally. > Seems not a problem on the current platforms, but I suppose that should be > replaced by SysFileSystem::MaximumPathLength ? > > Regards > Jean-Louis > > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > |