Sven Barth schrieb:
>> Although, as said: Only very few functions realy act on the file name.
>> Most use the file handle only (which will not change).
> Regarding the filename, yes, but while we're at it we could also
change functions like WriteFile to WriteFileW (etc.)...
There is no WriteFil
On 20.05.2012 10:58, Jürgen Hestermann wrote:
Sven Barth schrieb:
>> Although, as said: Only very few functions realy act on the file name.
>> Most use the file handle only (which will not change).
> Regarding the filename, yes, but while we're at it we could also
change functions like WriteFi
On 20 May 2012, at 02:59, Andrew Brunner wrote:
> I'm having a hard time with GDB and debugging threads on a OSX 10.7.4 with
> fpc/trunk
>
> The shipped gdb worked great with the exception of threads calling methods
> via synchronize (so I can debug).
What are you doing exactly, what happens, a
In "fpc\rtl\inc\file.inc" (and fpc\fpc\rtl\inc\text.inc) the declaration
of "Assign"
uses the generic "String" type for the file name. I think this can be
AnsiString too, so it may be longer than 255 characters.
But the assignment to the internal *rec element "name" (which
is "array[0..255] of ch
On Sun, May 20, 2012 14:40, Jürgen Hestermann wrote:
> In "fpc\rtl\inc\file.inc" (and fpc\fpc\rtl\inc\text.inc) the declaration
> of "Assign"
> uses the generic "String" type for the file name. I think this can be
> AnsiString too, so it may be longer than 255 characters.
> But the assignment to th
>
>
> What are you doing exactly, what happens, and what is the expected result
> instead?
>
I'm upgrading my gdb from shipping version with darwin to gdb version from
download. I downloaded and ran /configure make make install 7.1. It
doesn't work with fpc. I'm going to have to switch back. T
On 20 May 2012, at 15:25, Andrew Brunner wrote:
>> What are you doing exactly, what happens, and what is the expected result
>> instead?
>
> I'm upgrading my gdb from shipping version with darwin to gdb version from
The above was a question relating to "... with the exception of threads calling
On Sun, May 20, 2012 at 8:52 AM, Jonas Maebe The
above was a question relating to "... with the exception of threads calling
methods via synchronize (so I can debug)." I.e., what are the exact things
you are doing, what is happening, and what are the expected results
regarding trying to debug thre
Tomas Hajny schrieb:
On Sun, May 20, 2012 14:40, Jürgen Hestermann wrote:
Move(s[1],TextRec(t).Name,Length(s));
That would be a bug IMO when S is longer than 255 characters.
"Move" does no range check.
No, unit System (which uses these include files) is never compiled with $H+.
Ok. I
Am 21.05.2012 07:17 schrieb "Jürgen Hestermann" :
>
>
>
> Tomas Hajny schrieb:
>>
>> On Sun, May 20, 2012 14:40, Jürgen Hestermann wrote:
>>
>>>
>>> Move(s[1],TextRec(t).Name,Length(s));
>>> That would be a bug IMO when S is longer than 255 characters.
>>> "Move" does no range check.
>>>
>>
>> No,
10 matches
Mail list logo