Path: utzoo!utgpu!attcan!uunet!zephyr!tektronix!reed!keithb
From: keithb@reed.UUCP (Keith Brown)
Newsgroups: comp.unix.microport
Subject: Re: Curses bug in V/AT 2.4 - what was i
Message-ID: <12883@reed.UUCP>
Date: 19 Jun 89 08:56:57 GMT
References: <353@osc.COM> <42700022@osiris.cso.uiuc.edu>
Reply-To: keithb@reed.UUCP (Keith Brown)
Organization: Reed College, Portland OR
Lines: 22

>is that endwin() does not release allocated memory.
>
>#include <curses.h>
>    {
>	printf ("Executing loop number: %d\r", i);
>	initscr ();
>	endwin ();
>    }

It's not supposed to release the memory.  endwin() just restores your
tty to a sane mode so you can shell.  As soon as you return from the shell,
you may do a refresh() and poof, you've got your screen back, everything in
place to continue executing.  But one user having 90 of these, a bit beyond
my remembering how far down the stack I am.
 
-Keith

-- 
Keith Brown
UUCP:  {decvax allegra ucbcad ucbvax hplabs}!tektronix!reed!keithb
BITNET: keith@reed.BITNET       ARPA: keithb%reed.bitnet@cunyvm.cuny.edu
CSNET: reed!keithb@Tektronix.CSNET     CIS: 72615,216