From: Mike McCarty (jmccarty_at_ssd.usa.alcatel.com)
Date: 2001-08-13 22:19:17
On Mon, 13 Aug 2001, M Ancher wrote:
> On Mon, Aug 13, 2001 at 09:47:25PM +0200, groepaz wrote:
> > mmmh well.... that is a (_THE_) problem indeed... if we want tight
> > code, we can only have ONE gfx-mode (and we dont need all those
> > functions that deal with finding out the current or available
> > gfx-mode or resolution) - and if we want a flexible library, we will end
> > up with loads of dead code linked in. ... mmmmh ... sounds to me as if having
> > a set of simelar functions for each gfx-mode in a seperate module
> > which you'd have to select (link in) at compile time.
>
> How about
>
> #include <graphics.h>
> #include <graph160.h>
>
> for 160x200.
>
> or
>
> #include <graphics.h>
> #include <graphall.h>
>
> if all modes are needed.
>
> This solution make programs small if needed, or flexible if needed.
Another technique I have seen used is something like this:
#define GR_NEED GR_NEED_ALL
#include <graphics.h>
or
#define GR_NEED (GR_NEED_160 | GR_NEED_480)
#include <graphics.h>
Mike
--
char *p="char *p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
I can explain it for you, but I can't understand it for you.
I don't speak for Alcatel <- They make me say that.
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo_at_musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.
This archive was generated by hypermail 2.1.3 : 2001-12-14 22:05:41 CET