Comments on: Public and Private meaningless in v2 components

By: Bob Staple

Bob Staple — Wed, 17 Nov 2004 12:40:04 +0000

Guten Tag - Hier ist ein sehr schooner Site. Cheap Staples

Danke!
Bob Staple

By: Grand

Grand — Tue, 02 Nov 2004 22:36:10 +0000

Hello there,

Iwas browsing the web and found this blog. Some interesting quotes. Keep them coming!

Alice
Grand

By: Vera

Vera — Mon, 17 Nov 2003 07:45:41 +0000

Sounds like a good topic for Nigel’s new blog.

By: Sam

Sam — Mon, 17 Nov 2003 04:13:41 +0000

You’re absolutely right, if someone were to go ahead and add public/private to anything, they wouldn’t be able to distribute changes. I heard MM was working on the EULA issue so let’s all cross our fingers.

Besides, it wouldn’t be wise for anyone other than MM to make any changes. Changing classes that aren’t in a namespace you own could break other things so even if your intentions are benign, it’s something to avoid.

A reference list would serve the same purpose though and not break anything or violate the EULA…

By: robby

robby — Mon, 17 Nov 2003 03:56:51 +0000

Don’t forget, (as I understand it) even if a set of developers were to go in and clean up the ‘mess’ left behind, they couldn’t technically do anything about it as the EULA kinda kills any developer based work on the sent class files.