Re: Nontrivial examples of C interface with Ada

[tmoran@bix.com]

>stop calling it a "binding" and start calling it a "subsystem" or
  Take a look at www.adapower.com in the list under "Win32 bindings".
Clearly several of those are what you would call subsystems, not bindings.
I suggest we adopt the idea of R-values of insulation thickness.  Then an
R-1 binding is Ada syntax, acceptable to an Ada compiler, but C in spirit,
ie, pass pointers, return flags, etc.  I'd say an R-4 binding has
exceptions and types, but still a 1-1 map between C functions and Ada
procedures.  I'd call CLAW an R-15, say, because it does indeed insulate
you from many of the characteristics of the C API, but still follows the
general outline.  In particular, your program built with CLAW will have
the "look and feel" of a Windows program to its users.  A platform
independent "subsystem", eg GtkAda or Tcl/Tk, would be labeled R-50 - you
have an internal environment that is almost totally independent of the
external environment.
  If you don't like that, then at least let's have a less general term
than "subsystem". ;)