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
On 9/1/13, Jonas Maebe wrote:
> Correct.
Thanks for the explanations.
Bart
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
On 01 Sep 2013, at 16:34, Bart wrote:
> 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?
Correct.
Jonas___
fpc-pascal maillist
On 9/1/13, Marco van de Voort wrote:
> 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
On 1 Sep 13, at 14:32, Marco van de Voort wrote:
> In our previous episode, Bart said:
> > > As I wrote -
> > > the other file and directory related functions and procedures have
> > > always had only shortstring interfaces, whereas with GetDir there has
> > > also been the ansistring version).
> >
In our previous episode, Bart said:
> > As I wrote -
> > the other file and directory related functions and procedures have
> > always had only shortstring interfaces, whereas with GetDir there has
> > also been the ansistring version).
>
> I would prefer waiting for _all_ IO functions to handle L
On 8/31/13, Tomas Hajny wrote:
> That probably depends on the level of urgency this issue has for you.
ATM it does not happen in real world scenarios for me.
> As I wrote -
> the other file and directory related functions and procedures have
> always had only shortstring interfaces, whereas with
