Is C++ dead?

[Disch]

EDIT:

apparently I should read the rest of your post before replying. XD

Whatever, I give up. Maybe it isn't polymorphism.

[chrisname]

@Disch,
I thought you might find this interesting. /proc is where the scheduler creates a directory/file structure for every running process. As an example, here's an instance of bash:
http://i45.tinypic.com/vgmmw1.png
That shows it's directory (which is no longer existing; the first PID I can see is 1430 and that's probably my login shell. The rest are all >=1800) which is 1639 because that was it's PID. The fd folder is the folder of file descriptors it has open:
http://i46.tinypic.com/mbigk3.png
There, you can see the instance of bash had four files open. 0, 1 and 2 are stdin, stdout and stderr, respectively. I don't know what 255 refers to, perhaps that's a reserved file that the kernel uses for signal handling or something.

It's weird that all these operations are done on files. You'd think it'd be pretty slow, accessing the hard disk for everything...

Actually, that's wrong. It doesn't. It does all that in memory and then syncs the disks.

[helios]

It does all that in memory and then syncs the disks.

Oh, come on. I though you were going to say something smarter than that.
Of course using /proc doesn't touch the HDD at all.

[chrisname]

Oh of course! It's all in memory! Like the initial ramdisk, or ramfs or cpio or whatever it's called now! That makes so much more sense. That's a really clever abstraction. [Edit: Does the "exe" file refer to the executable's location in memory (i.e. it's stored EIP value) so the kernel can resume from there?]

I though you were going to say something smarter than that.

:3