leppie wrote: Won't it be funny if Microsoft actually buys Adobe (there was some rumours about that)? Only if they fire him again. Regards, Nish My technology blog: voidnish.wordpress.com

Ashish Kaila wrote: So if you are coding in C++ do you ensure a level lower than that i.e. assembly is doing the right thing? Nice example. Watcom C++ does exactly that, and I always love that (back when I was hacking around with VGA VESA modes and and mode-x.) Ashish Kaila wrote: Ever heard of separation of concerns in OOP? Guess not Also a nice example, but less enjoyable things. I guess you mix up "separation of concerns" with "encapsulation of concerns". The first is just a prerequisite (you can't place a platform dependency behind an interface for an exchangable implementation if it is mixed up with other responsibilities). OO doesn't get rid of these nasty parts, it just helps you deal with them. Inside every there's still a printf. When OO was introduced, there was a lot of pressure to "rewrite everything", just so it adheres to "OO standards". Instead of considering possibilities how to fit existing libraries into the new paradigm, they were cast away behind wrappers. I know it's hard and probably not solvable in the general case. But a an attempt, I give you this[^]. Agh! Reality! My Archnemesis![^] | FoldWithUs! | sighist | WhoIncludes - Analyzing C++ include file hierarchy

The might of your sword is legendary Sire! There is only one Ashley Judd and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.

Leave my balls alone, would you... (You're all thinking it, I just had the balls to say it) I wasn't, now I am, then I won't be anymore.

Well, exactly this is the reason, why C# was invented... :)

Draw a red circle whit a slash through it (the classic 'No' symbol), and put TLA in the middle. Karl

The Microsoft Automatic Graph Layout (MSAGL) component is something you could use: http://research.microsoft.com/en-us/projects/msagl/[^]

Vasudevan Deepak Kumar wrote: I would say you should have pointed out in the article's own message board so that the author can address this and give you a more quality tool. Well Said. Best Regards, Mushq Mushtaque Ahmed Nizamani Software Engineer Ultimus Pakistan

Hi, You are confusing between boot-loader & OS. (1) Bootloader is the initial stage program which will ultimately load final OS. It is of fixed size(512 bytes). But if your boot-loader goes beyond this size you can cut this in pieces leaving the intent of bootloader intact. Boot -loader is basically written in assembly(8086 or higher). (2) Os is....you know what it is. So once you power ON your system; it will perform normal BIOS routines & then cheks for boot sequence. According to boot sequence it will verify first sector (512 bytes)for validity & if it is valid it will load that sector in RAM. And later pass control to it. Here starts the job of boot-loader which should take care of loading all imp files reqd for loading OS ultimately. if you have more doubts feel free to contact me.

The idea is to avoid namespace name clashes. The domain names should be uniqu, so you can at least avoid name clashes with components from other companies. It's actually a good practice, and nothing keeps you from using it in C++ and .NET. "After all it's just text at the end of the day. - Colin Davies "For example, when a VB programmer comes to my house, they may say 'does your pool need cleaning, sir ?' " - Christian Graus