delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1999/07/20/09:00:35

Date: Tue, 20 Jul 1999 15:57:59 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Anders David Skarin <hobbit AT swipnet DOT se>
cc: djgpp AT delorie DOT com
Subject: Re: Problems whith passing commandline args
In-Reply-To: <37944FC9.89B57A6A@swipnet.se>
Message-ID: <Pine.SUN.3.91.990720155405.20658A-100000@is>
MIME-Version: 1.0
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

On Tue, 20 Jul 1999, Anders David Skarin wrote:

> I have a strange problem (at least if i define it), when 
> passing command line arguments longer than 2 characters (+3 dos file
> type) to my 3d-engine my vesa routines will not find the mode i 
> want to use. (this works perfectly if you pass 2+3 char arguments)
> 
> The only thing i can think of that might be causing the problem 
> is DJGPPs internal transfer buffer (__tb), which I use to collect
> mode/card information in my vesa routines. 

Please explain more about what you are trying to do.  A sample code that 
shows this would be nice.

> Does anyone know if DJGPP uses this buffer for commandline args, 
> and in the process somehow corrupts it?

DJGPP uses the transfer buffer to pass command-line arguments, but only 
when you invoke one DJGPP program from another.  It is not clear from 
your description whether this is what your code does.

In general, you cannot assume that the contents of the transfer buffer 
stay unaltered across library function calls, because low-level library 
functions would use the transfer buffer at will.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019