Re: alternate window creation

[Thomas Dickey]

On Tue, 24 Feb 2009, Bryan Christ wrote:

> I guess my answer would be don't call delwin() but instead call free()
> (or don't call anything for autos).  Would there be a reclamation
> problem with that?  For example:  struct ldat *_line

yes - none of the implementations that I recall allocates a window as
a single chunk of memory.

> On Tue, 2009-02-24 at 22:16 +0000, Thomas Dickey wrote:
> > On Tue, 24 Feb 2009, Bryan Christ wrote:
> >
> > > Neither.  I would like to create a WINDOW but supply the storage space
> > > myself whether it be auto or malloc()
> >
> > I'm reasonably sure that's not portable.
> >
> > What should happen, for instance, if you call delwin on a copy?
> >
> > > On Tue, 2009-02-24 at 21:14 +0000, Thomas Dickey wrote:
> > > > On Tue, Feb 24, 2009 at 11:26:03AM -0600, Bryan Christ wrote:
> > > > > I'm looking for a way to do this:
> > > > >
> > > > > WINDOW  my_win1;
> > > > > new_win(&my_win,10,10,1,1);  /* <--pseudo func */
> > > >
> > > > I'm not sure whether you're looking for subwin() or dupwin().

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net