Chris

I’m going to have to start over… a buddy left some less than clean software on my pc, and I ended up with a pretty bad rootkit. I had to wipe two drives on my desktop, reform two of our personal laptops, get a new Xbox 360, and re-flash the firmware on my modem & router because of it. Nasty stuff. I’m still in the process of getting new financial info; debit cards, credit cards, bank account numbers, paypal, etc.

Symantec failed. Prevx failed. And not surprisingly, MS’ Defender failed as well. Don’t have a name for it, but, anyone reading this, be on alert. It’s not been fun.

Hopefully this weekend I’ll get some one-on-one time with it, again.

Thanks for expressing interest in it. Like I said, it’s been a fun project so far. Not uber-complicated.. just trying to make sure I accommodate for as many layout-style cases as I can before I turn it loose. (definitely honing my regular expression skills!)

Thank you for the comment and hope to hear more from you soon…

I stopped writing my post because I started writing a script that would do this for me on existing files. It’s panning out alright so far… have a few more features to implement, then will make it public. (didn’t look to see if anything exists for it yet, but it’s a fun little project.)

- Commenting -
About the commenting style… I always think it looks nice, but, my boss actually drove it home to me that /**/ comment style should be reserved for block commenting CODE while debugging, rather than notes.

It’s pretty irritating to get into an old project (that is less than OO friendly/themed…) and start commenting sections of code, then have to change the original comment style just so you can debug. It’s easily avoided by using # and or //.

Now, I do bend the rule a bit… When I am documenting an object, or contents of a file (at the TOP of the page). I think block comments OUTSIDE class/method/function definitions are OK. But, I still use # and // as much as possible any other time.

The only other exceptions I have to this rule are Java and CSS. I don’t have to work much with Java but even then, I use a lot of // to start the comment line. CSS forces you to use /**/ so… I do. :)

Ultimately, it’s preference, yes… If you’re the only developer, and are a good OOPer, you’re probably fine using block commenting. Don’t be surprised if the project moves to another [set of] developer[s], and one or two of them gripe about it though. :)

I should just update and publish my post… TO BE CONTINUED? We’ll see. :)

Cheers – welcome back.

For the Last.FM class I encountered a problem when dealing with arguments (user= or artist=) that have spaces in them. I solved the issue by doing the following:

$lastfm->artist_getInfo(“artist=” . urlencode(“Test Artist”))

which makes the text URL friendly since it is being called through a URL. However I’m sure there is a way to fix it in the class but I don’t understand the code you provided since it is a little above my head.

Great article by the way! The last.fm and cache modules are very helpful.

Looking forward to giving it a whirl.