Gone quiet here

Hmm, Its hard though when you learn one way to try to keep the bits you do
know and connect them to the new concepts.


Still for most of the things I need on a daily basis I never need to go down
that road.

One of the issues that seems to occur now is that a writing environment
often exists that people use and that is fine if it respects standard APIs
for accessibility. Take for example Revo uninstaller. the previous version
was very accessible in Windows, the current one is completely unaccessible
though to the sighted it just looks more modern, what is missing are the
events to trigger access tech to know where buttons are when its a list and
what position you are in the lists etc.

Brian

--
----- -
This newsgroup posting comes to you directly from...
The Sofa of Brian Gaff...

Blind user, so no pictures please!
"Jeff Findley" wrote in message
...
In article ,
says...

One of the things I find hard are the new lamps for old object orientated
basis of many of them. The fact of the matter is that objects are just
multi
dimensioned arrays with various differently specified elements.

That's merely the beginning of what object oriented encompasses. Yes,
object oriented puts behavior (virtual function tables) where it
belongs, conceptually on the objects themselves. But, it's far more
than that. OO is the foundation of modern interface driven software
design. Polymorphism, multiple inheritance, and memory management of
these objects are also key features of the language. Add other bits
like the C++ Standard Template Library and you've got yourself a
powerful language.

Most all of what I've written over the last 20+ years is OO implemented
in C++. Done the right way, it's easy to maintain and extend. Roles
and responsibilities can be clearly assigned to various classes. So
when a bug pops up or an extension needs to be made, it's clear what
needs to be "touched". This is simply not as easy to do with procedural
code, which tends to evolve into "spaghetti code" over the years and any
change tends to involve "touches" all over the system making it brittle.

I suppose its easier to use object than arrays as you do not need to
remember abstract addresses of the various dimensions and coordinates of
the
data inside.

That and so much more. OO languages add constructors and destructors so
that initialization and clean-up are *always* performed. It's too easy
to miss stuff like that in a procedural language.

Jeff
--
All opinions posted by me on Usenet News are mine, and mine alone.
These posts do not reflect the opinions of my family, friends,
employer, or any organization that I am a member of.