Mail Archives: djgpp/1999/11/03/23:43:29
From: | "BP" <bport AT direct DOT ca>
|
Newsgroups: | comp.os.msdos.djgpp
|
References: | <9mmT3.825$cn1 DOT 10505 AT typhoon-sf DOT snfc21 DOT pbi DOT net>
|
Subject: | Re: A few quasi-newbie questions
|
Lines: | 42
|
Organization: | EAC
|
X-Priority: | 3
|
X-MSMail-Priority: | Normal
|
X-Newsreader: | Microsoft Outlook Express 5.00.2314.1300
|
X-MimeOLE: | Produced By Microsoft MimeOLE V5.00.2314.1300
|
Message-ID: | <wgTT3.4814$LX2.239478@brie.direct.ca>
|
Date: | Wed, 3 Nov 1999 01:44:02 -0800
|
NNTP-Posting-Host: | 216.66.139.27
|
X-Complaints-To: | abuse AT direct DOT ca
|
X-Trace: | brie.direct.ca 941621404 216.66.139.27 (Wed, 03 Nov 1999 01:30:04 PST)
|
NNTP-Posting-Date: | Wed, 03 Nov 1999 01:30:04 PST
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Reply-To: | djgpp AT delorie DOT com
|
Response to Question 1: Rhide 1.4.7 stable? I've tried it. It has some bug
fixes such as being able to compile a file in a different directory, and a
bug with the default rhide options. I would use it, but it always crashes on
my machine after these two steps: compiling anything and then exiting Rhide.
I get a SIGSEGV error message. So, I use Rhide 14b. You'll just have to try
it out yourself, I guess. Probably be a good idea to back up your entire
djgpp directory before doing so, in case something unpredicatable occurs.
StarWeaver <starx AT pacbell DOT net> wrote in message
news:9mmT3.825$cn1 DOT 10505 AT typhoon-sf DOT snfc21 DOT pbi DOT net...
> While i'm still finding the whole DJGPP um, 'suite' to be a brainfull, i
think
> i've gotten the hang of most of it (I'm absolutily not new to either
windows
> or dos, or C :) i still have a few questions:
>
> (BTW thanks for the umpteen messages about -lstdcx & rhide, didn't even
need
> to ask... missed it in the faq too...)
>
> 1. Is RHIDE 1.4.7 stable enough to use? I would love to have the latest
> version but i don't know hoew buggy the beta is.
>
> 2. You're not supposed to use libg++ anymore, yet 'gxx' requires it.
Solution:
> Don't use 'gxx' ?
>
> 3. LibStdCxx seems to have less than spectacular documentation. I know how
to
> find a referance on STL and IOstreams (Which is what the faq said, i
think),
> but what about the several dozen headers in lang/cxx that don't seem to
> involve either of those packages? (I.E. IOstreams donsen't take up many
> headers i don't think, and i've found a lot of odd ones that arent listed
in
> the SGI/STL library information)
>
> Thanks for any help, sorry for any rambling...
>
> -StarWeaver Blue
- Raw text -