As an old Mumpster who did all of his programming in languages other than
Mumps before the advent of OO and as a result has tried to understand OO
without knowing anything about C++, Java, etc. I miss what is being said. I
would like to know what you mean by "tight coupling and poor cohesion we see
in the Vista code base".
Jim Gray
----- Original Message -----
From: "Gregory Woodhouse" <[EMAIL PROTECTED]>
To: <hardhats-members@lists.sourceforge.net>
Sent: Monday, July 11, 2005 5:24 PM
Subject: Re: [Hardhats-members] Data dictionary question...
My point of view is that OO can easily be done poorly (something that
bothers me -- a lot), but it can b incredibly powerful when done right.
Rather than being an "interesting aside", I see object orientation, or
something like it, as critical to the long range success of Vista. The
tight coupling and poor cohesion we see in the Vista code base is way,
way out of hand, and trying to move Vista into new environments only
makes the issue more acute. No, I don't think for a moment that using an
object oriented language will somehow magically solve these problems, but
I find it hard to envision a solution that doesn't at least use basic
ideas of object orientation in a fundamental way.
In fact, I think it is part of the genius of Vista that it anticipated OO
technology to a surprising extent, and I doubt it would have been as
successful as it has been were that not the case.
===
Gregory Woodhouse
[EMAIL PROTECTED]
"Design quality doesn't ensure success, but design failure can ensure
failure."
--Kent Beck
On Jul 11, 2005, at 3:46 PM, Kevin Toppenberg wrote:
Speaking of discipline, its pretty clear that one
can't tie the hands of the programmer. It's like
Marty's analagy of the girlfriend and the motorcycle
again. :-)
But I don't see why garbage collection would be any
more of an issue with variables acting as object than
it would be with any other variable. A simple kill
would take them all out. For those stored in ^TMP
etc, if one set up an infrastructure that
"instantiated" the "objects" for the programmer, then
they could be put in locations that would be
immediately obvious that they were no longer in use. A
$J node would be a first thought.
I'm sure you put quite a bit of thought into this
before. I am just shooting from the hip. It was just
a thought that was buzzing around my head.
But to be honest, I find the benefits of an OO
oriented language to be most helpful when I am either
working with a graphic environment, or when using a
library like Borland's VCL. I don't know if I really
need OO in what I am doing now.
Kevin
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar
happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by
HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
