www.digitalmars.com Home | Search | C & C++ | D | DMDScript | News Groups | index | prev | next
Archives

D Programming
D
D.gnu
digitalmars.D
digitalmars.D.bugs
digitalmars.D.dtl
digitalmars.D.ide
digitalmars.D.dwt
digitalmars.D.announce
digitalmars.D.learn
digitalmars.D.debugger

C/C++ Programming
c++
c++.announce
c++.atl
c++.beta
c++.chat
c++.command-line
c++.dos
c++.dos.16-bits
c++.dos.32-bits
c++.idde
c++.mfc
c++.rtl
c++.stl
c++.stl.hp
c++.stl.port
c++.stl.sgi
c++.stlsoft
c++.windows
c++.windows.16-bits
c++.windows.32-bits
c++.wxwindows

digitalmars.empire
digitalmars.DMDScript
electronics




digitalmars.D.bugs - [Issue 2065] New: Return value of std.file.exists() is inverted.

↑ ↓ ← d-bugmail puremagic.com writes:
http://d.puremagic.com/issues/show_bug.cgi?id=2065

           Summary: Return value of std.file.exists() is inverted.
           Product: D
           Version: 2.014
          Platform: PC
               URL: http://dsource.org/projects/phobos/changeset/683
        OS/Version: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Phobos
        AssignedTo: andrei metalanguage.com
        ReportedBy: torhu yahoo.com


In r683, the Windows version of this function is changed into return the wrong
value.

The correct return statement would be "return result != 0xFFFFFFFF;"

The relevant docs:
http://msdn.microsoft.com/en-us/library/aa915578.aspx


-- 
May 02 2008
↑ ↓ → d-bugmail puremagic.com writes:
http://d.puremagic.com/issues/show_bug.cgi?id=2065


andrei metalanguage.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED




------- Comment #1 from andrei metalanguage.com  2008-05-03 11:25 -------
(In reply to comment #0)
 In r683, the Windows version of this function is changed into return the wrong
 value.
 
 The correct return statement would be "return result != 0xFFFFFFFF;"
 
 The relevant docs:
 http://msdn.microsoft.com/en-us/library/aa915578.aspx

Ouch. How did that ever go through? The fix will go into the next release. Thanks! --
May 03 2008