[fpc-pascal] ExpandFileName failure on long filenames on Linux

Marco van de Voort marcov at stack.nl
Sun Sep 1 20:38:19 CEST 2013


In our previous episode, Bart said:
> > That was the original idea, removing the shortstring versions for not
> > embedded targets, so that nobody accidentally could call shortstring
> > versions.  (and only find out runtime)
> >
> > But that was deemed to confusing, so now both sets are back again.
> 
> If I understand you correctly:
> This would mean that (in the cpstr branch) calling any IO function
> with LongStrings (or the like) will NOT suffer from the problems the
> shortstring counterparts have?

Yes, several problems were fixed. Mostly in the past they were considered
not worthwhile to fix (because it would only up from 255 to 260 chars).

Since in the unicode branch, the unicode functions are called that allow
longer strings (from memory: 8192 straight, and more with \\.\ prepended?),
it was decided to clean up all cases where there were shortstring only code
paths (like getdir).





More information about the fpc-pascal mailing list