The most cogent argument against the idea of creating and then
deleting has already been made:  Namely, sure, you can do it now, but
may not be able to in 10 seconds time.  Hypothesise that this is a
network share, and the network just pisadeared on you?  Some kind of
transactional system is the only way of this working reliably.

On 17 June 2010 21:01, silky <[email protected]> wrote:
> On Thu, Jun 17, 2010 at 8:53 PM, James Chapman-Smith
> <[email protected]> wrote:
>> Hi silky,
>>
>> It only creates then deletes folders that don't exist so nothing else (bar
>> some sort of file system watching rogue program) will write to those
>> folders.
>>
>> But what do you mean "terrible coding style"? The only thing that I can
>> fault is the use of the general-purpose `catch` statement.
>>
>> Please hit me with your criticisms. I want to learn. :-)
>
> I was kind of making a joke; no-one wants to hear me complain yet
> again about the appropriateness of "var". But I'm not a big fan of
> many changes in .NET, or Mr Scripting himself (he's probably not a bad
> guy, but I'm not a fan of many if any of the "dynamic" changes; but
> who knows, perhaps that attitude will change).
>
>
>> Cheers.
>>
>> James.
>
> --
> silky
>
>  http://www.programmingbranch.com/
>



-- 
Meski

"Going to Starbucks for coffee is like going to prison for sex. Sure,
you'll get it, but it's going to be rough" - Adam Hills

Reply via email to