Date:	Fri, 19 Oct 2001 14:58:51 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	ROLAND <roland_asmann AT yahoo DOT com>
Message-Id:	<1429-Fri19Oct2001145851+0200-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9
CC:	djgpp AT delorie DOT com
In-reply-to:	<20011019115211.40626.qmail@web9106.mail.yahoo.com> (message from
	ROLAND on Fri, 19 Oct 2001 04:52:11 -0700 (PDT))
Subject:	Re: problems with ioctl.h
References:	<20011019115211 DOT 40626 DOT qmail AT web9106 DOT mail DOT yahoo DOT com>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> Date: Fri, 19 Oct 2001 04:52:11 -0700 (PDT)
> From: ROLAND <roland_asmann AT yahoo DOT com>
> 
> --- Hans-Bernhard Broeker
> <broeker AT physik DOT rwth-aachen DOT de> wrote:
> > *What* definitions?  You definitely have to start
> > being a lot less
> > vague in your problem descriptions if anybody is
> > going to be able to
> > help you.  Show meaningful source fragments, or at
> > the very least the
> > error messages you get from your code.
> 
> My main question was: Will it be harmfull if I used
> the part in ioctl.h which was 'not available' by the
> #if 0 statement?

Yes, it could be harmful: many programs originally developed on Unix
look at the macros defined by the ifdef-ed-out part of ioctl.h and
assume that the related functionality in the library exists.  But
DJGPP doesn't yet support the Unix ioctl commands, so you will have
programs that compile and maybe even link, but either crash or do
other wrong things at run time.

So don't do that.

If you have specific problems with the ioctl.h macros, please explain
each one of them separately, and someone might suggest a work-around
for you.

- Raw text -