This post originated from an RSS feed registered with Ruby Buzz
by Daniel Berger.
Original Post: Things that make you go, "Huh"
Feed Title: Testing 1,2,3...
Feed URL: http://djberg96.livejournal.com/data/rss
Feed Description: A blog on Ruby and other stuff.
Not long ago, with the help of Park Heesob and teh intraweb, I came up with a program that would do a global search and replace. The goal was to replace all deprecated instances of "assert_raises" with "assert_raise". And, the code below works just dandy:
What totally threw me off is that, even after making the modifications, the mtime is the same! One of two things is happening. Either the modification is so fast (less than a second) that it doesn't update the mtime, or making changes via mmap won't update the mtime regardless.
Normally I wouldn't give a damn, except for one thing - it's confusing the bejesus out of Eclipse and its CVS integration. I've made a modification to the files locally (which I can see by manually inspecting them after the script has run), but it will NOT detect that the local file is different from the remote file, even if I explicitly check for it. I can only guess it's because the mtime is identical.