From: SourceForge.net <no...@so...> - 2007-02-23 05:52:18
|
Bugs item #1166659, was opened at 2005-03-19 13:40 Message generated for change (Comment added) made by miesfeld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1166659&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Pending >Resolution: Fixed Priority: 5 Private: No Submitted By: Walter (walter-pachl) >Assigned to: Mark Miesfeld (miesfeld) Summary: Incorrect value vrom Parse Source Initial Comment: /* REXX ****************************************************** * Datentrger in Laufwerk C: ist System * Volumeseriennummer: ECAE-D346 * * Verzeichnis von c:\test * * 19.03.2005 12:18 869 CAP.rex * 1 Datei(en) 869 Bytes * 0 Verzeichnis(se), 31.233.835.008 Bytes frei * --------------------------------------------------------------------- * v=OBJREXX 6.00 24 Apr 2002 * s=WindowsNT COMMAND c:\test\cap.REX * --------------------------------------------------------------------- * v=REXX-Regina_3.4beta1(MT) 5.00 14 Nov 2004 * s=WIN32 COMMAND c:\test\cap.rex * 19.03.2005 Walter Pachl Compare the file name CAP.rex with * the Parse Source results :-( ***************************************************************/ 'dir cap.*' Parse Version v Parse Source s Say 'v='v Say 's='s ---------------------------------------------------------------------- >Comment By: Mark Miesfeld (miesfeld) Date: 2007-02-22 21:52 Message: Logged In: YES user_id=191588 Originator: NO It looks to me like Walter's original complaint was that parse source was returning cap.REX when the actual file name was CAP.rex. I no longer see that, but it may be that it was a file system behavior that has been altered by one of the many service packs or fixes that Microsoft has done since April 2002. However, the current code will, under the right circumstances return the MS-DOS short file name for parse source. It will also return different capitalization than the actual file name. I wrote a slightly different test program than Walter's to show that. I also have a fix, tested on W2K, W2K3, and XP on FAT, FAT32, and NTFS. Output from the test, before and after the fix: /* Existing behavior */ C:\test>myCap.rex myCap.rex v=REXX-ooRexx_3.1(MT) 6.00 20 Feb 2007 s=WindowsNT COMMAND C:\test\myCap.rex In ALongFunctionName(), called using: ALongFunctionName ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 20 Feb 2007 s=WindowsNT FUNCTION C:\test\ALongFunctionName.rex In ALongFunctionName(), called using: alONGfUNCTIONnAME ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 20 Feb 2007 s=WindowsNT FUNCTION C:\test\alONGfUNCTIONnAME.rex In ALongFunctionName(), called using: ALongFunctionName, no quotes ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 20 Feb 2007 s=WindowsNT FUNCTION C:\test\ALONGFUNCTIONNAME.rex In ALongFunctionName(), called using: ALONGF~1 ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 20 Feb 2007 s=WindowsNT FUNCTION C:\test\ALONGF~1.rex /* Smallest change will only fix the 'DOS short name' problem. * Does not fix the capitalization problem. */ C:\test>myCap.rex myCap.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT COMMAND C:\test\myCap.rex In ALongFunctionName(), called using: ALongFunctionName ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT FUNCTION C:\test\ALongFunctionName.rex In ALongFunctionName(), called using: alONGfUNCTIONnAME ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT FUNCTION C:\test\alONGfUNCTIONnAME.rex In ALongFunctionName(), called using: ALongFunctionName, no quotes ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT FUNCTION C:\test\ALONGFUNCTIONNAME.rex In ALongFunctionName(), called using: ALONGF~1 ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT FUNCTION C:\test\ALongFunctionName.rex /* Complete fix. but it involves an additional open and close * of a file handle, and a string copy. */ C:\test>myCap.rex myCap.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT COMMAND C:\test\myCap.rex In ALongFunctionName(), called using: ALongFunctionName ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT FUNCTION C:\test\ALongFunctionName.rex In ALongFunctionName(), called using: alONGfUNCTIONnAME ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT FUNCTION C:\test\ALongFunctionName.rex In ALongFunctionName(), called using: ALongFunctionName, no quotes ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT FUNCTION C:\test\ALongFunctionName.rex In ALongFunctionName(), called using: ALONGF~1 ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT FUNCTION C:\test\ALongFunctionName.rex File Added: capTest.zip ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1166659&group_id=119701 |
From: SourceForge.net <no...@so...> - 2007-04-20 19:56:47
|
Bugs item #1166659, was opened at 2005-03-19 15:40 Message generated for change (Settings changed) made by wdashley You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1166659&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Walter (walter-pachl) Assigned to: Mark Miesfeld (miesfeld) Summary: Incorrect value vrom Parse Source Initial Comment: /* REXX ****************************************************** * Datentrger in Laufwerk C: ist System * Volumeseriennummer: ECAE-D346 * * Verzeichnis von c:\test * * 19.03.2005 12:18 869 CAP.rex * 1 Datei(en) 869 Bytes * 0 Verzeichnis(se), 31.233.835.008 Bytes frei * --------------------------------------------------------------------- * v=OBJREXX 6.00 24 Apr 2002 * s=WindowsNT COMMAND c:\test\cap.REX * --------------------------------------------------------------------- * v=REXX-Regina_3.4beta1(MT) 5.00 14 Nov 2004 * s=WIN32 COMMAND c:\test\cap.rex * 19.03.2005 Walter Pachl Compare the file name CAP.rex with * the Parse Source results :-( ***************************************************************/ 'dir cap.*' Parse Version v Parse Source s Say 'v='v Say 's='s ---------------------------------------------------------------------- Comment By: Mark Miesfeld (miesfeld) Date: 2007-02-22 23:52 Message: Logged In: YES user_id=191588 Originator: NO It looks to me like Walter's original complaint was that parse source was returning cap.REX when the actual file name was CAP.rex. I no longer see that, but it may be that it was a file system behavior that has been altered by one of the many service packs or fixes that Microsoft has done since April 2002. However, the current code will, under the right circumstances return the MS-DOS short file name for parse source. It will also return different capitalization than the actual file name. I wrote a slightly different test program than Walter's to show that. I also have a fix, tested on W2K, W2K3, and XP on FAT, FAT32, and NTFS. Output from the test, before and after the fix: /* Existing behavior */ C:\test>myCap.rex myCap.rex v=REXX-ooRexx_3.1(MT) 6.00 20 Feb 2007 s=WindowsNT COMMAND C:\test\myCap.rex In ALongFunctionName(), called using: ALongFunctionName ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 20 Feb 2007 s=WindowsNT FUNCTION C:\test\ALongFunctionName.rex In ALongFunctionName(), called using: alONGfUNCTIONnAME ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 20 Feb 2007 s=WindowsNT FUNCTION C:\test\alONGfUNCTIONnAME.rex In ALongFunctionName(), called using: ALongFunctionName, no quotes ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 20 Feb 2007 s=WindowsNT FUNCTION C:\test\ALONGFUNCTIONNAME.rex In ALongFunctionName(), called using: ALONGF~1 ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 20 Feb 2007 s=WindowsNT FUNCTION C:\test\ALONGF~1.rex /* Smallest change will only fix the 'DOS short name' problem. * Does not fix the capitalization problem. */ C:\test>myCap.rex myCap.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT COMMAND C:\test\myCap.rex In ALongFunctionName(), called using: ALongFunctionName ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT FUNCTION C:\test\ALongFunctionName.rex In ALongFunctionName(), called using: alONGfUNCTIONnAME ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT FUNCTION C:\test\alONGfUNCTIONnAME.rex In ALongFunctionName(), called using: ALongFunctionName, no quotes ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT FUNCTION C:\test\ALONGFUNCTIONNAME.rex In ALongFunctionName(), called using: ALONGF~1 ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT FUNCTION C:\test\ALongFunctionName.rex /* Complete fix. but it involves an additional open and close * of a file handle, and a string copy. */ C:\test>myCap.rex myCap.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT COMMAND C:\test\myCap.rex In ALongFunctionName(), called using: ALongFunctionName ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT FUNCTION C:\test\ALongFunctionName.rex In ALongFunctionName(), called using: alONGfUNCTIONnAME ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT FUNCTION C:\test\ALongFunctionName.rex In ALongFunctionName(), called using: ALongFunctionName, no quotes ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT FUNCTION C:\test\ALongFunctionName.rex In ALongFunctionName(), called using: ALONGF~1 ALongFunctionName.rex v=REXX-ooRexx_3.1(MT) 6.00 22 Feb 2007 s=WindowsNT FUNCTION C:\test\ALongFunctionName.rex File Added: capTest.zip ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1166659&group_id=119701 |