Thanks, my fault. Didn't know that behavior. Consider myself educated :)
-- Sent from my Palm Pre Evan Prodromou wrote: One of the most annoying bugs to track down in PHP is when there's some whitespace after a closing ?> in a library. This will get emitted to the browser, which then assumes that output has begun, and blows a casket if you try to set any headers or do real output. The easy workaround is to leave out the closing tags. They're not necessary and the risk is greater than the reward. I've just bounced a change in 0.8.x that added closing tags to all the .php files in the scripts/ directory. Although these are command-line scripts, and thus have less risk for whitespace-after-closing-tags bugs, I'd still like to leave them out. Thanks, -Evan -- Evan Prodromou CEO, StatusNet, Inc. [email protected] - http://identi.ca/evan - +1-514-554-3826
_______________________________________________ StatusNet-dev mailing list [email protected] http://lists.status.net/mailman/listinfo/statusnet-dev
