revDeleteFolder and Lessons Learned..

[Dave Cragg]

On 8 Jul 2005, at 12:22, Alex Tweedly wrote:

> Chipp Walters wrote:
>
>
>> Hi Dave,
>>
>> Well, since I passed revDeleteFolder a single "/" and it tried to  
>> delete (w/out being able to be interrupted) the *entire* hard  
>> disk, I would say it's less dangerous to 'roll your own'. I would  
>> expect revDeleteFolder to take as an argument a valid path,  
>> including drive letter. For instance I would expect:
>>
>> revDeleteFolder "C:/"
>>
>> to delete the C drive. I don't know why just "/" does it and I'm  
>> afraid to test it with a null, especially since it can't be  
>> interrupted. Anything you roll on your own can be interrupted with  
>> a control-period.
>>
>>
> "/" works  because "/" is a valid directory specifier for Rev. You  
> can do
>    set the defaultFolder to "/"
> and it does; you don't need a drive specifier.
> Come to think of it, you can do it in a Windows shell (or whatever  
> a DOS box is called these days) - "cd \"  works.

Interesting, as
   there is a folder "/"
returns false on XP and true on OS X. Which could prove an insidious  
danger.


> I think it would be good to have an optional parameter pConfirm  
> which would require a user confirmation for each directory (or  
> maybe even each file ?). That would make it much more "comfortable"  
> to develop and test an application without fear of inadvertently  
> passing a bad starting directory, and the parameter could be  
> reverted to (the default of) "off" before shipping.

Sounds good.

Cheers
Dave