Also, if your PHP script segfaults the webserver (at least in apache) you won't get anything either, because the data in the buffer heading towards the client will get eaten by the crashing apache child.
In this instance, you'll not only need decent error checking, but you'll likely have to add lots of 'print checkpoint1';flush();' to your code to figure out what's killing it.
But Vincent is right in the sense that if you're tossing @ signs in your code, you HAVE to be checking for errors, because users just hate a page that isn't working (or worse, partly working) but throwing no errors.
Better to leave a generic system error message peaking through than to have no error message at all.