Re: seek() bug?

new topic     » goto parent     » topic index » view thread      » older message » newer message

On 14 Feb 2002, at 21:55, Robert Craig wrote:

> 
> Kat writes:
> > The comma looks like it's part of the 'j' in some fonts. 
> 
> Yes, I can see that now.
> With the font I'm using, the comma is only about 2 pixels.
> It extends the hook on the j a tiny bit, rather than 
> appearing as a separate character.

Well, i'm so glad that is solved. <sigh> Clinton argued over the meaning of 
"is", but we are still on individual chars. <sigh>

Now, after working on seek() and where() for 3 days, the puts() is still not 
puts()ing where i told the program to seek() to. Both gets()ing and then 
where()ing and subtracting the length(readline)+1 , or where()ing and then 
gets()ing,, the seek()ing *seems* to work, but the puts() lands 100's or 
1000's or 10,000's of bytes in the wrong place. I can't see how the puts() 
lands so far away, when length(readline) = 30. Seek() was a wonderful tool in 
pascal for not get()ing 50meg files, and now i need to do() that in Eu.

So is there a buglist for seek? Is seek() maybe allergic to long filenames, or 
filenames with sp aces in them? 

Jeffrey Fielding's WIN32FIL.EW saved my tail yesterday. Little things like 
being able to access files is handy. <sigh> Perhaps there is a seek() in 
kernal32.dll i should be using? How? This should be native Eu code, how is a 
newbie to programming to find these things?

Kat

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu