For developers the following 3 constants are important and should exist in every wp-config.php of a development system. Please use it with precaution on a live system!

Add define(‘WP_DEBUG’, true); to wp-config.php to enable

the reporting of notices during development.

Add define(‘WP_DEBUG_DISPLAY’, false); to wp-config.php to

disable the display of errors.

Add define(‘WP_DEBUG_LOG’, true); to wp-config.php to log

eerrors to debug.log in the wp-content directory.

Sets PHP error handling and handles WordPress debug mode.

A small syntax with huge impact. I recommend this to everyone who is developing with WordPress, especially with Xdebug a fantastic help.

via WordPress Developer Hint – WordPress, EALL, define’WPDEBUGLOG’, define’WPDEBUGDISPLAY’, define’WPDEBUG’, Xdebug – WP Engineer.

Give your business a web presence or spruce up your current site design in no time with this season’s special deal. Just contact us and mention the keyword WINTERDEAL and we will apply a discount to the total cost of your project.

-10% starting at $1,000
-15% starting at $2,500
-20% starting at $4,000

Expires: 4/15/2011

This release reinforces the commitment Microsoft are making to F#, including F# in Visual Studio. As explained in my PDC10 lecture The Future of F#, we have a clear vision for F#, indeed a ground-breaking one, and are investing in it. To augment this, we are glad to be able to provide a compiler/library source drop, and are excited about the role this can play for education and tool development.

This source code is under the Apache 2.0 license and is published as part of the F# PowerPack codeplex project, which is now also under the Apache 2.0 license. The F# PowerPack now includes libraries, tools and the compiler/library source code drops.

I’d like to take a moment to explain the F# team’s approach to this. Firstly, the source for the F# compiler in our MSI/CTP releases has been available for some time, in the releases themselves, so in that sense there’s not much new in this release. Secondly, we’ve always made sure we have a free download binary release of F# available, and will continue to do that, and that should still be the main way you “get” a release of F#. However, we’ve long discussed making compiler+library source available in a different way.

After some discussion, we’ve decided to do this via a “code drop” model, where we make available versions of the compiler+library code logically matching each release of the F# language itself. In the F# team, releases of F# are matched to coincide with releases of Visual Studio itself: using this release cadence simplifies our development processes and gives clarity to language versioning. This means the code we are making available today is for the F# 2.0 language, released in April 2010, including the small changes for the MSI tools updates through November 2010.  We expect to make matching code drops if/when service pack(s) of Visual Studio 2010 are released, though sometimes it may take a while for us to get that out the door.

As this release is a code drop, it does not contain binaries. This means you still get F# from fsharp.net, so the place to “get” F# doesn’t change with this release.

To get or learn F# 2.0, or learn why F# is important, go to fsharp.net

To use F# 2.0 in Visual Studio 2008 or Visual Studio 2010, including with the freely available Visual Studio 2010 Shell go to fsharp.net

To get the compiler+library source code drop, go to the F# PowerPack and look for directory compiler.

Enjoy!

Don, for the F# team

via Announcing the F# Compiler + Library Source Code Drop – Don Syme’s WebLog on F# and Related Topics – Site Home – MSDN Blogs.

Click here to read article by Mike Pilgrim to get the insights on the next step of the Web.