Mail Archives: djgpp/1998/02/10/11:01:45
Thanks Tom, you've been more than helpful, you've been downright
informative, which is good, because I'd rather be told why instead of just
do. With the help of you all I managed to compile hello world. (I also
understand how this whole thing works a little better)
I compiled hello.c and hello.cpp
But I can't link the .o files, and cant select the run option in RHIDE.
(posted under Arrgh). But I'm over the first hurdle, and understand enough
now to put the program aside for a while, sit down and work throught the
docs a second time.
I'll check if the faq I have is 2.10, and if it isn't I'll get it
> >
> > And as far as being silent forever, believe me, by now, I am so humbled
by
> > my ignorance, I'd love to be silent.
> Sorry, but this a (hmm... "stupid" is way too hard, but you'll get the
> idea ;-)
> behavior. If you want ignorant support, telling you that there are no
> bugs in
> this and that program, but you use it the wrong way, stick to MS (1).
>
> There are no stupid questions, only frequent ones. Generally, if there
> is something
> unclear, there is always a chance to make it clearer, if there is a bug,
> one can
> have it fixed. You do have the chance. Don't waste it.
>
Point taken. It's just as a 3.9 student, I'm a little ashamed by my
ignorance in any field, especially considering the conddescending nature of
usenet.
side note: If a question is frequent yet covered in the readme and the faq,
can the problem possibly lie somewhere other than people not reading the
documentation. Obviously, it can, and I suggestions are out there to combat
this. I'm going to need to start a thesis soon, and though you may not
think of it as such, a readme is a very special form of communication, as
is a faq. They are quite distinct from instructions or directions by nature
of having different intentions, and different history. Anyhow, hopefully I
can get my first program running soon.
Be true
- Raw text -