Mail Archives: djgpp/1997/02/10/22:25:44
From: | "John M. Aldrich" <fighteer AT cs DOT com>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Re: Some RHIDE problems
|
Date: | Mon, 10 Feb 1997 18:49:51 -0800
|
Organization: | Two pounds of chaos and a pinch of salt
|
Lines: | 33
|
Message-ID: | <32FFDE4F.7D68@cs.com>
|
References: | <01bc1633$a3c6f700$ee038cd0 AT wahander>
|
Reply-To: | fighteer AT cs DOT com
|
NNTP-Posting-Host: | ppp204.cs.com
|
Mime-Version: | 1.0
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Josh Anderson wrote:
>
> Third: Traceback eips don't work right
> Well, only if it's in an included file. Okay pseudo code example.
>
> main.c
>
> #include "somefile.c"
>
> main
This is not an RHIDE bug but a limitation of the default format used by
DJGPP to store debugging information.
Stylistic tip: You should never use the #include directive to include
actual program code into another source module. The only things that
should go in header files are #defines, struct and type definitions, and
global variable and function declarations. If you have code in multiple
source files, you should compile each file separately and link them into
the finished executable. RHIDE allows you to do this automatically by
inserting additional source files into your projects. If you need tips
on how to do this on the command line, just ask and someone will help
you.
If you follow the above standards, you should never need to worry about
crashes occurring inside included code.
--
---------------------------------------------------------------------
| John M. Aldrich, aka Fighteer I | fighteer AT cs DOT com |
| Plan: To find ANYONE willing to | http://www.cs.com/fighteer |
| play Descent 2 on DWANGO! | Tagline: <this space for rent> |
---------------------------------------------------------------------
- Raw text -