> However, my version *did* have one important difference -- according
> to MSDN, _MAX_PATH is defined in stdlib.h, which isn't #included by
> maxpathname.cpp, so you need to add that.
Done.
> If path_name_max() is to be used, in place of MAX_PATH in the
> _fullpath() call, should it not also be
Werner Lemberg wrote:
> thanks for the patch. I've simplified it a bit: Your _MAX_PATH code is
> now in maxpathname.cpp. Please test.
I also thought of doing that, and arrived at much the same modification to
maxpathname.cpp as you have. However, my version *did* have one important
difference -
Keith,
thanks for the patch. I've simplified it a bit: Your _MAX_PATH code is
now in maxpathname.cpp. Please test.
Werner
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
On Monday 25 April 2005 3:19 pm, Werner LEMBERG wrote:
> > The problem appears to be due to the use of `realpath()' in
> > `relocate.cpp'; the native Win32 equivalent for this function is
> > `_fullpath()', and the semantics are different. It could probably
> > be fixed with an appropriate `#defin
> The problem appears to be due to the use of `realpath()' in
> `relocate.cpp'; the native Win32 equivalent for this function is
> `_fullpath()', and the semantics are different. It could probably
> be fixed with an appropriate `#define' in `nonposix.h', or, if this
> module is specific to Win32
