Re^2: Unit testing OS rich code

[Voronich]

in reply to Re: Unit testing OS rich code
in thread Unit testing OS rich code

I really don't much care about the timestamp. I'm using touch as the quickest easiest way to create an empty file.

[BrowserUk]

the quickest easiest way to create an empty file.

Quickest? Definitely not. Easiest? Your call :)

cmpthese 1, {
    a=>q[ qx[ touch         junka.$_  ] for 1 .. 1000 ],
    b=>q[ do{ open my $f, ">junkb.$_" } for 1 .. 1000 ],
};;

  s/iter     a     b
a   8.83    --  -95%
b  0.421 1997%    --

[Voronich]

Certainly quickest for the programmer. This has to create 5 sentinel files every 3 months.

Love that profiling snippet. Gonna have to pull that for meeting arguments ;)

[eyepopslikeamosquito]

I'm using touch as the quickest easiest way to create an empty file

Are you seriously arguing that using:

`touch $file`

to create an empty file should be preferred to, for example:

{
   open(my $fh, '>', $file) or die "error creating empty '$file': $!";
}

on the grounds that it is "quicker and easier" to write?

If you are that stretched for time, how on earth do you expect to find time to write your proposed test mock framework?

[Voronich]

Good grief. I'm in fact not "seriously arguing" anything at all, least of all what someone 'should' be doing.

[chromatic]

I've written worse, and despite the qx// in void context, the desired behavior is a lot more obvious.

(I use File::Touch myself.)