Color me unimpressed with Perforce's keyword expansion.
if ( ( -f $File::Find::name ) && ( $_ =~ /.eml$/i ) ) {
becomes:
if ( ( -f $File: //messagegate/MAP/tools/runmail-db.pl $_ =~ /.eml$/i ) ) {
Since I use File::Find only all the time, no problem. Of course, Perforce's byzantine user interface always helps matters.
This blog is now hosted at consciou.us
Friday, September 28, 2007
Perforce considered harmful
Posted by Bradley at 1:59 PM
Labels: productivity
Subscribe to:
Post Comments (Atom)
1 comment:
Why do you have keyword expansion turned on if you don't want it to expand keywords?
That's not specific to Perforce. Any revision control system that does RCS-style keyword expansion would do that.
The +k filetype is what causes $File$ to be replaced. You can change this behavior with
p4 edit -t text+x filename.pl
Post a Comment