Frans Bouma's blog

Jimmy Nilsson blogs about AOP, or Aspect Oriented Programming.His article combines some different insights on the matter, good links to articles about AOP and is a good starting point for the people who have ignored AOP for a long time and find this the right moment to get started with AOP and what the fuss is all about.

Ralf Westphal has written an excellent article about Objectspaces and orthogonal design. Highly recommended food for your mind.

Paul Wilson blogs:

In fact, several have went out of there way to tell me how much the hostile attitudes of Frans and Thomas had turned them off!

S.B Chatterjee refers to an article which is a follow up on a blog by Michael Earls concerning a .NET reality check. (If this sentence sounds a little complex, it is, but just start with Michael's excellent blog entry and you're on track :))

Today I've posted this as a reply in the Microsoft.public.objectspaces newsgroup. I think it's also blogging material, so that's why I post it here too. You can decide to react here, on your own blog, but also in the microsoft.public.objectspaces newsgroup, available on the msnews.microsoft.com USENET server.

Disclaimer
Although I find it absurd to put in a disclaimer, I know for a fact that talking about Multiple Inheritance (MI) is risky, because it is one of those subjects which can cause irrational reactions, resulting in flame-fests. Discussions about MI should be theoretical and thus based on theory, not about one of the many different implementations. I'm discussing the theoretical benefits of MI and am not discussing a real implementation like C++'s MI. I've done some research on this subject prior to writing this article and have read many discussions about MI and .NET and also discussions about MI and languages like Eiffel, so I'm aware of the disadvantages of MI, I also am aware of the reasons (of the ones that are publicly stated) why .NET doesn't have MI at the moment. Still I think .NET contains enough functionality and implementations of classes and interfaces which require MI to be fully utilized. MI is a complex concept, however so is the concept of generics. MI can result in unmaintainable code, but so can Single Inheritance (SI) (any language can be used to write unmaintainable, bad code). You can work around MI in most situations, but you can also work around the lack of polymorphism (in C for example, by using function pointers) or even OO. Still it's seen as an advantage to have OO, polymorphism and (soon) generics.

I wish everyone a happy, good, healthy, warm and above all, .net-ful, 2004! :)

Ok, it's finished! :) Yesterday I blogged about my Christmas coding session resulting in an OpenGL 3D effect I named 'Bands' and today I've transfered it into a screensaver, complete with .Text / Weblogs.asp.net textures, to say 'Thank you' to Scott and the other people who keep this blogging site running, in a more 'geeky' fashion.