Newsgroups: comp.lang.c
Path: utzoo!utdoe!david
From: david@doe.utoronto.ca (David Megginson)
Subject: Re: Curses and portability question.
Message-ID: <1990Dec12.143050.28489@doe.utoronto.ca>
Organization: Dictionary of Old English Project - U of Toronto
References: <1990Dec10.110403.139@vax1.mankato.msus.edu>
Date: Wed, 12 Dec 90 14:30:50 GMT

In article <1990Dec10.110403.139@vax1.mankato.msus.edu> accwork@vax1.mankato.msus.edu writes:
>
>I am writing a program, which i hope to maintain a high level of portability. 
>But i also want to some screen management.  I was planning on using curses.  Is
>this a "good" choice ?  Is their something that is more standard ?  I hope to
>keep the portability accross a vax, and a pc.  So is their any chance of this ?
>
>thanks for your time.
>   brian.
>--
>Brian D. Goecke
>Mankato State University
>Accademic Computer Center Programmer.
>accwork@vax1.mankato.msus.edu
>   

There is a good curses library for GCC on the Atari ST, and I have seen at
least one for the PC. The most important thing about portability will be
to remember that sizeof(int) != sizeof(void *) on many machines (the
reason why porting sloppily-written Unix code can be hell). Also, on
some machines, malloc() takes an int argument, while under ANSI C, it can
take a (size_t) argument, where size_t _could_ be (long) or (unsigned long).


David Megginson
-- 
////////////////////////////////////////////////////////////////////////
/  David Megginson                      david@doe.utoronto.ca          /
/  Centre for Medieval Studies          meggin@vm.epas.utoronto.ca     /
////////////////////////////////////////////////////////////////////////