After a barrage of blog posts and primers from the guys on the other side of the fence, it appears that today might be the day that System.Web.MVC is released.
To say that I am excited would be an understatement. Mainstream acceptance and support (from the big machine) means that we can now propose this style of development without fear of recrimination from cowering/OSS averse decision makers. To me this is the most powerful component of this release as it is by no means revolutionary from a technology standpoint.
I have the perfect project for MVC sitting in the wings and I can now unleash. Thanks Microsoft for having the vision to support the concepts that we developers hold dear. I accept that things from MS will never be on the bleeding edge, but at least they are beginning to get a lot closer.
I can't wait. Bring on the CTP!
So they say that you learn something new everyday. They are correct today.
Digging through open source code is a great way to learn new tricks and I have been doing a fair bit of it lately - out of both necessity and curiosity. This is probably old hat to some but to me the following code is a bright and shiny hat of confusion:
public JobDetails GetNextJobToProcess()
{
//crazy for loop syntax here ...
for (;;)
{
BaseJobStore cachedJobStore = jobStore;
if (cachedJobStore == null)
return null;
JobDetails jobDetails = jobStore.GetNextJobToProcessOrWaitUntilSignaled(schedulerGuid);
if (jobDetails != null)
return jobDetails;
}
}
Turns out that the syntax represents an infinite for loop without any initialisation, conditions or increments. Might come in handy one day and these things are always good to know. I found a great article for explaining the intricacies of the for loop at Blackwasp.
Bonus points for anyone who can recognise the project the code belongs to!!!
