There is a difference between "information" and "instruction".
Information of a complex nature is often useless to people without some
kind of
instruction. Telling someone what something does is not the same as
explaining how and when to use it.
I banged my head against the - to me then - opaque gcc compilation
instructions when I first encountered it in the form of DJGPP. I was used
to TurboC++ and its IDE.
When I started using Linux fulltime, and I started reading makefiles, etc,
it started to make sense. "gcc -o hello hello.c" makes sense to me now.
"mingw32-gcc -I resource.h simplewindow simplewindow.c" is where I'm
struggling now. (And the GNAT compilation instructions, as well. I still
haven't got the hang of them. gnat-bind ... uh, yes
It's all a matter of degree.
Wesley Parish
--
"Good, late in to more rewarding well."  "Well, you tonight.  And I was
lookintelligent woman of Ming home.  I trust you with a tender silence."  I
get a word into my hands, a different and unbelike, probably - 'she
fortunate fat woman', wrong word.  I think to me, I justupid.
Let not emacs meta-X dissociate-press write your romantic dialogs...!!!