From: Damian Yerrick Newsgroups: comp.os.msdos.djgpp Subject: Re: Allegro exclusions... Organization: Pin Eight Software http://pineight.8m.com/ Message-ID: References: X-Newsreader: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 40 X-Trace: +r2abgOzdZzKNbMbNJueoxwvt8el/DIze0dT//PjBuReY8wv6q0AJSyvzFZaqDJTEXTTi+2AqKgV!rCpByCfqpMbQi0GBx4+ATBvU19Hy3RLNYDR8qY52U+doczciHFUdwtZ24RLM6LPmqMzIY0MANeAS!8UZ1aQ== X-Complaints-To: abuse AT gte DOT net X-Abuse-Info: Please be sure to forward a copy of ALL headers X-Abuse-Info: Otherwise we will be unable to process your complaint properly NNTP-Posting-Date: Fri, 22 Sep 2000 06:14:38 GMT Distribution: world Date: Fri, 22 Sep 2000 06:14:38 GMT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com On Fri, 22 Sep 2000 04:30:39 GMT, "JS" wrote: > What's the deal with the Allegro exclusions? In the documentation >it tells you to write them as: > BEGIN_whatever (whatever) > END_whatever... > However, every sample I've seen has the lines written as >'DECLARE_whatever...' rather than 'BEGIN_whatever...'. Also, there is no >'END_whatever' before moving on to the next list of drivers... What's up >with that?... DECLARE_foo_DRIVER_LIST is the old, deprecated syntax. BEGIN_foo_DRIVER_LIST...END_foo_DRIVER_LIST is the new syntax. For example, this code fragment (after #include ) is useful in commandline Allegro programs (e.g. dat.exe): BEGIN_JOYSTICK_DRIVER_LIST END_JOYSTICK_DRIVER_LIST BEGIN_MIDI_DRIVER_LIST END_MIDI_DRIVER_LIST BEGIN_DIGI_DRIVER_LIST END_DIGI_DRIVER_LIST BEGIN_GFX_DRIVER_LIST END_GFX_DRIVER_LIST >What's worse is that after installing the latest version of Allegro, >even THAT doesn't work! aarrgg!!! Excluding drivers works only on DJGPP and Watcom, where Allegro is statically linked. What error message does it give? --