On 8/31/13, Tomas Hajny <xhaj...@hajny.biz> wrote: > Now, as you have already found out yourself too, it is not an issue with > ExpandFileName only, but also with the overloaded version of GetDir > returning ansistring but still limited to 255 characters. I could provide > a workaround for ExpandFileName (using SysUtils.GetCurrentDir and > basically replicating the implementation of System.GetDir under Windows > except for using ansistrings), but fixing the ansistring overloaded > version of System.GetDir sound as a more appropriate option to me. >
I was unable to test under Windows, but because the offending code is in a generic inc file, I suspect it happens on Windows as well. On Linux I saw several file related functions that seem to handle only shortstrings... Should I file a bugreport? Bart _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
