Romain, I completely agree here, there should be absolutely no @ error supression in symfony core. If you find these cases, please file tickets, and lets get them fixed.
- Dustin On 3/25/09 9:39 AM, "Romain Dorgueil" <[email protected]> wrote: > consider thoose as a very bad practise, that should be avoided as much as > possible. There is many case where using "@" will cause debugging headaches, > and it's often used only because the developper is lazy and don't want to > handle non-fatal errors. > > The major problem is when the non-fatal error become an unpredicted fatal > error for whatever reason. PHP then nicely hide it and ruins your day by the > way. > > Remember that hiding and avoiding warnings/notices is not at all the same > thing. > > I agree there is a very few case in which the use of @-statements is required, > often because of poorly written builtins/extensions of PHP, but that's really > a rare case and their use should be strictly limitted to that, imho. > > Seeing more and more places in symfony where @-statements appears i'm starting > to see red elephpants as warnings... (111 code lines starts by '@' and 107 > contains "something = @...", som --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
