[Oorexx-bugs] [ oorexx-Bugs-1897792 ] SysTempFileName generates identical filenames

[SourceForge.net <no...@so...>]

Bugs item #1897792, was opened at 2008-02-20 07:28
Message generated for change (Comment added) made by bigrixx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1897792&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: External Functions
Group: 3.2.0
>Status: Closed
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: SysTempFileName generates identical filenames

Initial Comment:
-- ooRexx
say SysTempFileName(Value(TEMP,, "ENVIRONMENT")"FuBar_?????");
say SysTempFileName(Value(TEMP,, "ENVIRONMENT")"FuBar_?????");
say SysTempFileName(Value(TEMP,, "ENVIRONMENT")"FuBar_?????");

D04...@in...
2K3 server
Intel Xeon 3.2GHz (2 CPU) 

----------------------------------------------------------------------

>Comment By: Rick McGuire (bigrixx)
Date: 2008-02-23 14:02

Message:
Logged In: YES 
user_id=1125291
Originator: NO

Jon has diagnosed this correctly.  The SysTempFileName() function only
guarantees that it will return a name for a file that does not exist in the
target location.  Since this program is not creating the actual temp file,
it's bypassing the mechanism used to determine the suitability of the
returned name. 

----------------------------------------------------------------------

Comment By: Jon Wolfers (sahananda)
Date: 2008-02-23 02:30

Message:
Logged In: YES 
user_id=667060
Originator: NO

I can confirm that I also see this behaviour (3.2.0 on WXP).

I'm not sure that this is a bug.  The documentation says SysTempFileName
'Returns a unique name for a file or directory that does not currently
exist.'

The use of the term unique here might be the cause of the confusion.  As
the OP does not create a file based on the return from the first call, one
could consider it valid that sysTempFileName returned the same file name
again, because at the time of the call, a file with the first name does not
exist.

hth

Jon


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=684730&aid=1897792&group_id=119701