Re: [OT] Best way to isolate a GUI?

["Marin David Condic" <mcondic.auntie.spam@acm.org>]

Why would you want to use a variant record when a tagged type solves the
problem so much more elegantly? I've always found variant records to be a
pain in the posterior - in particular as noted by Randy that you have to
define everything in one place. If you wanted to pass back to an app various
events (or widget data, for that matter) it would seem that a base class of
some sort of "event" or "message" would be the place to start. You then
build up from that class the specific events or messages you need in
separate packages. If something gets added on top that message catalog,
you're not impacting anything else and the extension doesn't force
recompilation of the whole world.

Short of possibly efficiency concerns or representation issues, I just don't
see much excuse for variant records when we've got tagged types.

MDC
--
======================================================================
Marin David Condic
I work for: http://www.belcan.com/
My project is: http://www.jsf.mil/

Send Replies To: m c o n d i c @ a c m . o r g

    "Going cold turkey isn't as delicious as it sounds."
        -- H. Simpson
======================================================================

Warren W. Gay VE3WWG <ve3wwg@cogeco.ca> wrote in message
news:3E52A1BF.1020809@cogeco.ca...
>
> You brought some interesting points to the discussion, but none
> that would convince me that variant records are unsuitable for
> the job. The only point that came close IMHO was the possible
> overhead factor. That was a good point, but in my mind, probably
> not enough reason to avoid it.
>