Warnings and coding standards

[Infected]

Pixelpost is great, but the amount of warnings bothers me. I've removed most warnings from the admin panel and I'm going to do the same with the frontend.
This because 'error_reporting(0)' is not an option for me (a warning has its reason, so I do NOT want to ignore them. And usually it's easy to fix).
But what's the reason for ignoring these warnings? Is there a reason for it, or is it just 'lazyness'??

Also: What about coding standards? Do you use/have them?

[jaywilliams]

In the upcoming versions, one of the priorities is to fix the numerous warnings generated by the code.

This should be complete at the very latest v2.0.

[GeoS]

I.e. any output (caused i.e. by misconfigured box) can disable redirection headers and so on. This is one of main reasons why its off.