Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #105573

Re: Problems with lcc-win32 (trimmed)

Show all headers | View raw

Robert Wessel <robertwessel2@yahoo.com> writes:
>On Tue, 07 Mar 2017 15:02:00 GMT, scott@slp53.sl.home (Scott Lurndal)
>wrote:
>
>>mertesthomas@gmail.com writes:
>>>On Tuesday, March 7, 2017 at 18:50:31 UTC+1 jacobnavia wrote:=20
>>>> Le 07/03/2017 =C3=A0 13:50, mertesthomas a =C3=A9crit :
>>>> > In the meantime I stumbled over the function fseeki64().
>>>> > The call fseeki64(4, 54, 0) returns 54.
>>>>=20
>>>> ????
>>>>=20
>>>> fseek takes
>>>> 1) File pointer (first arg)
>>>> 2) offset
>>>> 3) "FROM parameter
>>>>=20
>>>> What is that "4" doing there?
>>>
>>>Sorry, I just copied my debug log, which contained the
>>>file descriptor number (fd). The actual call of fseeki64()
>>>uses a FILE pointer, as you said.
>>>
>>>Probably fseeki64() tries to return the resulting offset
>>>location, like lseek() does. But fseek() and fseeki64()
>>>are defined different and they should return 0 on success.
>>
>>Had to look that one up.  I see  it is a microsoft private
>>interface only required because they chose to make 'long'
>>32-bits on amd64/x86_64 systems.
>
>
>In MS's defense, _fseeki64 has been part of their 32-bit C library for
>a long time.  The notion that the file offset could be limited to 32
>bits was broken a decade before C89 was finished.

My issue was with MS choosing to define 'long' as 32-bits, when it
makes much more sense for long and pointers to be the same size,
particularly when building applications for both 32-bit and 64-bit
operating environments.

Back to comp.lang.c | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Problems with lcc-win32 mertesthomas@gmail.com - 2017-03-05 14:12 -0800
  Re: Problems with lcc-win32 luser droog <luser.droog@gmail.com> - 2017-03-05 14:46 -0800
    Re: Problems with lcc-win32 gazelle@shell.xmission.com (Kenny McCormack) - 2017-03-05 22:57 +0000
    Re: Problems with lcc-win32 jacob navia <jacob@jacob.remcomp.fr> - 2017-03-06 00:49 +0100
      Re: Problems with lcc-win32 luser droog <luser.droog@gmail.com> - 2017-03-05 22:10 -0800
  Re: Problems with lcc-win32 BartC <bc@freeuk.com> - 2017-03-05 23:32 +0000
    Re: Problems with lcc-win32 jacob navia <jacob@jacob.remcomp.fr> - 2017-03-06 00:48 +0100
  Re: Problems with lcc-win32 jacob navia <jacob@jacob.remcomp.fr> - 2017-03-06 00:44 +0100
    Re: Problems with lcc-win32 BartC <bc@freeuk.com> - 2017-03-06 00:13 +0000
    Re: Problems with lcc-win32 Keith Thompson <kst-u@mib.org> - 2017-03-05 19:35 -0800
      Re: Problems with lcc-win32 David Brown <david.brown@hesbynett.no> - 2017-03-06 10:26 +0100
        Re: Problems with lcc-win32 James Kuyper <jameskuyper@verizon.net> - 2017-03-06 07:08 -0500
        Re: Problems with lcc-win32 Keith Thompson <kst-u@mib.org> - 2017-03-06 08:37 -0800
          Re: Problems with lcc-win32 David Brown <david.brown@hesbynett.no> - 2017-03-06 21:16 +0100
      Re: Problems with lcc-win32 jm.bourguet@gmail.com - 2017-03-06 06:54 -0800
        Re: Problems with lcc-win32 David Brown <david.brown@hesbynett.no> - 2017-03-06 17:18 +0100
          Re: Problems with lcc-win32 Keith Thompson <kst-u@mib.org> - 2017-03-06 08:42 -0800
            Re: Problems with lcc-win32 David Brown <david.brown@hesbynett.no> - 2017-03-06 21:19 +0100
          Re: Problems with lcc-win32 jm.bourguet@gmail.com - 2017-03-06 08:44 -0800
            Re: Problems with lcc-win32 David Brown <david.brown@hesbynett.no> - 2017-03-06 21:20 +0100
    Re: Problems with lcc-win32 mertesthomas@gmail.com - 2017-03-06 00:24 -0800
  Re: Problems with lcc-win32 jacobnavia <jacob@jacob.remcomp.fr> - 2017-03-06 18:15 +0100
    Re: Problems with lcc-win32 (trimmed) jacobnavia <jacob@jacob.remcomp.fr> - 2017-03-06 18:50 +0100
      Re: Problems with lcc-win32 (trimmed) mertesthomas@gmail.com - 2017-03-07 04:50 -0800
        Re: Problems with lcc-win32 (trimmed) jacobnavia <jacob@jacob.remcomp.fr> - 2017-03-07 14:54 +0100
          Re: Problems with lcc-win32 (trimmed) mertesthomas@gmail.com - 2017-03-07 06:20 -0800
            Re: Problems with lcc-win32 (trimmed) scott@slp53.sl.home (Scott Lurndal) - 2017-03-07 15:02 +0000
              Re: Problems with lcc-win32 (trimmed) mertesthomas@gmail.com - 2017-03-07 08:00 -0800
                Re: Problems with lcc-win32 (trimmed) jacobnavia <jacob@jacob.remcomp.fr> - 2017-03-07 20:30 +0100
                Re: Problems with lcc-win32 (trimmed) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-03-08 01:06 +0000
                Re: Problems with lcc-win32 (trimmed) jacobnavia <jacob@jacob.remcomp.fr> - 2017-03-08 12:17 +0100
                Assigning a struct to an integer (Was: Problems with lcc-win32 (trimmed)) gazelle@shell.xmission.com (Kenny McCormack) - 2017-03-08 11:40 +0000
                Re: Problems with lcc-win32 (trimmed) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-03-08 11:51 +0000
              Re: Problems with lcc-win32 (trimmed) Robert Wessel <robertwessel2@yahoo.com> - 2017-03-07 15:27 -0600
                Re: Problems with lcc-win32 (trimmed) scott@slp53.sl.home (Scott Lurndal) - 2017-03-08 13:50 +0000
                Re: Problems with lcc-win32 (trimmed) scott@slp53.sl.home (Scott Lurndal) - 2017-03-08 13:51 +0000

csiph-web