Menu ▾ ▴

Found what seem like a bug

Open Discussion
awsdert
2023-01-20
2023-08-29

  • awsdert

    awsdert - 2023-01-20

    In fileapi.h line 29 there's this line:

    if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) || _WIN32_WINNT >= _WIN32_WINNT_WIN10

    The problem with this is that it prevents compiling when using
    FileSetPointer, FileSetPointerEx &/or FlushFile. The 1st condition is
    fine but those functions are definitely available in earlier versions
    of windows so there's no reason they should be hidden behind that. I
    even tried setting WINAPI_FAMILY directly to WINAPI_PARTITION_DESKTOP
    only to find that nothing is defined instead, if I had been compiling
    for the metro api then sure that would make sense but no, I'm
    compiling for win32 & win64 api's, there's absolutely no reason for
    these vital functions to be undeclared

     

    • awsdert

      awsdert - 2023-01-20

      Never mind, I'm a numpty, didn't realise I had the wrong name for the
      function, was supposed to be using SetFilePointer, guessing the same
      happened with FlushFile

      On Fri, 20 Jan 2023 at 12:10, Lee Shallis gb2985@gmail.com wrote:

      In fileapi.h line 29 there's this line:

      if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) || _WIN32_WINNT >= _WIN32_WINNT_WIN10

      The problem with this is that it prevents compiling when using
      FileSetPointer, FileSetPointerEx &/or FlushFile. The 1st condition is
      fine but those functions are definitely available in earlier versions
      of windows so there's no reason they should be hidden behind that. I
      even tried setting WINAPI_FAMILY directly to WINAPI_PARTITION_DESKTOP
      only to find that nothing is defined instead, if I had been compiling
      for the metro api then sure that would make sense but no, I'm
      compiling for win32 & win64 api's, there's absolutely no reason for
      these vital functions to be undeclared

       

Log in to post a comment.