www/porting.html - diff

Return to porting.html CVS log

Up to [local] / www

version 1.10, 1998/08/13 23:11:18

version 1.11, 1998/08/18 02:49:25

Line 266

``new curses''. Change:<br>

<code>ncurses.h ==> curses.h</code><br>

<code>-lncurses ==> -lcurses</code><br>

``Old curses'' is available as <code>ocurses.h/libocurses</code>.

``old (BSD) curses'' is available by defining <code>_USE_OLD_CURSES_</code>

<li>In OpenBSD, terminal discipline has been upgraded from the older <code>sgtty</code>

before including <code>curses.h</code> (usually in a Makefile) and

standard BSD <code>fcntl</code> to the newer POSIX <code>tcgetattr</code> family.

linking with <code>-lcurses</code>.

<li>In OpenBSD, terminal discipline has been upgraded from the older BSD

<code>sgtty</code> to the newer POSIX <code>tcgetattr</code> family.

Avoid the older style in new code. Some code may define <code>tcgetattr</code>

to be a synonym for the older <code>fcntl</code>, but this is at best a stopgap

to be a synonym for the older <code>sgtty</code>, but this is at best a stopgap

measure on OpenBSD. The <code>xterm</code> source code is a very good example of

what not to do.

Try to get your system functionality right: you want a type that remembers

Line 283

Line 285

you should leave your terminal in a sane state. Do your tests under an

older shell, such as sh, which does not reset the terminal in any way at

program's termination.

<li>The newer termcap and curses, as included with OpenBSD, include standard sequences

<li>The newer termcap/terminfo and curses, as included with OpenBSD, include standard sequences

for controlling color terminals. You should use these if possible, reverting

to standard ANSI color sequences on other systems. However, some terminal descriptions

have not been updated yet, and you may need to be able to specify these sequences manually.