There has been one thing that has driven me crazy since the begining days of my php programming. I understand that using @ to suppress errors can be useful. But what I don’t understand is why php would ever want to suppress a fatal error. Normally if @function() causes a fatal error, the error will still be displayed. However, if you do @include(’file’) and there is a fatal error in that file, you get a blank page.

So if you develop in php, please try to never suppress errors from an included file. There are other ways of catching warnings and displaying your own messages, but I need those fatal errors to help me to continue developing with your software.

I use webfaction to host a lot of my django projects. It has an easy setup that will get you developing quickly and a great community of talented programmers. There is also a quick setup for rails, wordpress, and a lot more.

Related posts:

  1. How To Use Triggers to Track Changes in MySQL  Setting constraints and rules in the database is better than writing special code to handle the same task since it...
  2. Web-Based Version Management  This is an idea to help with CyTE, but I’d like to start seeing this idea applied to other web-based...
  3. Programming Analogies  I like to think of programming languages as tools. It’s always best to use the right tool for the job…...