Re^3: Unique filenames with Time::HiRes

Replies are listed 'Best First'.
Re^4: Unique filenames with Time::HiRes by grinder (Bishop) on Jul 19, 2004 at 08:27 UTC
Maybe just append a random number Or maybe not. The OP states that the names must be in sequence. Consider two files created in the epoch second 1090225457. The first file is generated with the rand string 0.837 (rounded). Half a second later, still in the same epoch second, another file is created, and rand returns 0.238 (rounded). The second file will sort before the first... The same critism can be made of beable's solution elsewhere in this thread. - another intruder with the mooring of the heat of the Perl	[reply]
Re^5: Unique filenames with Time::HiRes by bsb (Priest) on Jul 21, 2004 at 01:33 UTC
Granted. Although I'm not sure that one of the other being "first" makes much sense at that granularity, although it'll depend on the problem. I guess I'm more suspicious of the OP's conception of the problem and the need for "independent" processes to syncronize in this way. Seems like there'd be a better solution than sequentially naming files but there wasn't enough detail to judge.	[reply]
Re^5: Unique filenames with Time::HiRes by beable (Friar) on Jul 19, 2004 at 08:32 UTC
Sure, you can make that criticism. But if you think about it, when you read the files in directory order, as long as you don't sort the files, you'll get them in the order they were created. Therefore, appending a random number is a perfectly acceptable method of generating the unique file names. Except for the small possibility of getting the same filename...	[reply]
Re^6: Unique filenames with Time::HiRes by DrHyde (Prior) on Jul 20, 2004 at 08:09 UTC
when you read the files in directory order, as long as you don't sort the files, you'll get them in the order they were created. I think you're making a huge assumption there about the filesystem. `perldoc -f readdir` and `man 3 readdir` say nothing about the order of the directory entries they give you.	[reply] [d/l] [select]