Feedster

Just a note that while I am going to be working on Feedster most / all of the weekend, I'm probably not going to blog much about it if at all.  I'll save stuff for Monday when more people are listening.  But if you want to see what someone else thinks of Feedster, see Brent.   I'll do a better job of blogging it on Monday but suffice it to say that Brent ... (see for yourself).

Oh and should you not care about Feedster a whit / wonder when or if I'm ever going to talk about something else, here's a PHP debugging tip.  And the answer is probably next week you'll see more of my usual blather. 

Tip: Debugging Large PHP Scripts

This is probably obvious to a lot of folks but generally not beginners.  PHP's error handling is written such that if you miss a ; or ) or {, the error can be AT the line reported or before it.  Depending on the tokenization of the script, it could be way before it.  Some of the Feedster code is quite long now, at least by PHP standards, so what I've taken to doing is moving the closing ?> marker up to just after the line where the error is reported.  That makes finding it easier by that many lines.  Now it isn't quite as good when functions you use are located below the line (they have to be defined to run the script so you might have to move them up or comment them out).  Still I only said this was a *tip* not the *holy grail*.  Unfortunately there is no holy debugging grail except for this: Stop Programming.

Enjoy the weekend!  Anything you want to ask me about / comment on Feedster about, I'm online.

5:35:08 AM      Google It!   comment []    IM Me About This