Hal Vaughan said:
<snip>
>
> So I create protofunctions in a header and include that instead of the
> actual source file, right?
I can see nothing obviously wrong with Jim Langston's fine reply to this
bit, so I'll move on to your next question.
> Richard Heathfield wrote:
>
>> To make the files all work together, you have to "link" them.
>>
>> In gcc, it works like this:
>>
>> gcc ...lots of flags and stuff... -c -o foo.o foo.c
>> gcc ...lots of flags and stuff... -c -o bar.o bar.c
>> gcc ...lots of flags and stuff... -c -o baz.o baz.c
>
> For some reason when I try gcc, I run into problems, so I've been using
> g++. I know it's to the same binary, but for some reason it only works
as
> g++. Are there implications to that which aren't obvious?
Oops - mea culpa. I keep assuming that people are using C, don't I? I tend
to forget that there are still one or two C++ users out there. ;-)
So - no, there are no non-obvious implications that obviously spring to
mind, but the very *non*-non-obvious implication is that you use g++ if
you're still struggling along with C++, and upgrade to gcc once you're
ready to make the leap to C.
> I've installed the C and C++ stuff in Eclipse, but I've been using a
text
> editor and the command line for now, while I'm getting use to it.
I don't bother with an IDE - I find that the command line is more
powerful,
for me at least. Of course, I do use a makefile, albeit a rather primitive
one. But it would be silly to be prescriptive about this. In fact, when
I'm on Windows, I /do/ use an IDE - but that doesn't happen very often
nowadays.
--
Richard Heathfield <http://www.cpax.org.uk>
Email: -http://www.
+rjh@[EMAIL PROTECTED]
users: <http://www.cpax.org.uk/prg/writings/googly.php>
"Usenet is a strange place" - dmr 29 July 1999
|
