ptember 04, 2006 5:34 PM
Subject: Re: [ql-users] bug in qlib_h C68 support file
> Hi Guys,
>
> Three things were fooling me:
>
> 1) I was calling this using a C function so I 'assumed' that it was
> converting to C strings
>
> 2) when I grab the string, if under 3
unkins" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 04, 2006 5:34 PM
Subject: Re: [ql-users] bug in qlib_h C68 support file
> Hi Guys,
>
> Three things were fooling me:
>
> 1) I was calling this using a C function so I 'assumed' that it wa
> floppy
> based systems. Those using hard disk based systems are better off
> using the
> commented versions
>
> Dave
> .
> - Original Message -----
> From: "James Hunkins" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, September 04,
Rich Mellor wrote:
> However, ideally the minimum surely has to be 36+5?? (rounded up to 42) or
> does the library have a distinct device name string also??
No, the device name is not part of the directory/file name.
Marcel
___
QL-Users Mailing List
ht
On Mon, 04 Sep 2006 15:49:18 +0100, Marcel Kilgus
<[EMAIL PROTECTED]> wrote:
> James Hunkins wrote:
>> I think that I found a bug in the qlib_h include file used by C68.
>> Here are the details:
>>
>> In the 'qdirect' structure, the member 'd_name' is defined as:
>> char d_name[36];
>
>
On Mon, 04 Sep 2006 15:18:59 +0100, James Hunkins <[EMAIL PROTECTED]>
wrote:
> Guys,
>
> I think that I found a bug in the qlib_h include file used by C68.
> Here are the details:
>
> In the 'qdirect' structure, the member 'd_name' is defined as:
> char d_name[36];
>
> This works as long a
floppy
based systems. Those using hard disk based systems are better off using the
commented versions
Dave
.
- Original Message -
From: "James Hunkins" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 04, 2006 3:18 PM
Subject: [ql-users] bug in q
James Hunkins wrote:
> I think that I found a bug in the qlib_h include file used by C68.
> Here are the details:
>
> In the 'qdirect' structure, the member 'd_name' is defined as:
> char d_name[36];
Your misconception is that d_name holds a null terminated string,
which it doesn't. The le
Guys,
I think that I found a bug in the qlib_h include file used by C68.
Here are the details:
In the 'qdirect' structure, the member 'd_name' is defined as:
char d_name[36];
This works as long as the directory/file name is 35 or fewer
characters and holds a properly terminated C st
