Re: A community Windows binding

["Steve" <nospam_steved94@comcast.net>]

"Jeffrey Carter" <spam@spam.com> wrote in message
news:KgH9d.9844$M05.267@newsread3.news.pas.earthlink.net...
> Nick Roberts wrote:
>
> > The window manager calls -- via callbacks, or (better) dispatching -- 
>
> Callbacks and dispatching are essentially the same thing in a windowing
> system. You have to write little pieces of code that can be invoked in
> any order at any time outside your control. You have to use global
> variables extensively for these little pieces of code to communicate.
> The code is difficult to read because you have to understand all these
> little pieces to understand any part of the software.
>

Don't confuse the architecture into which software must be developed
with poor design.  It is entirely possible to develop software that is
easy to follow in a windowing system... without resulting to using global
variables extensively for these little pieces of code to communicate.

For example: in windows a reference to an object may be associated with
a window.  The message handling routine has access to the window, and
likewise the reference to the object.  Nothing is global.  This may not be
the most obvious implementation, but is certainly more clean.

Steve
(The Duck)

> With an event queue approach, one writes standard imperative software
> using your standard imperative language (Ada's about the only one). The
> code is well structured and easy to read and understand.
>
> -- 
> Jeff Carter
> "I'm a lumberjack and I'm OK."
> Monty Python's Flying Circus
> 54
>