[M3devel] proposal for dealing with lazy console--please review and comment!

[rodney.bates]

I guess I am on a somewhat different wavelength on this.  I do
agree that a complete set of queries by the application should
be supported, concerning lazy allocated streams.  But to me,
applications need to have either very little or nothing in the
way of ability to change behaviour.

For one thing, it makes sense for the lazy property to apply
only to stdout/stderr, on win32 platforms, compiled as -gui.
This is why I was questioning getting a stream from FileWr.Open,
and then setting it lazy.  Laziness doesn't make any sense on
a disk file.

Beyond that, I think at the most, an application should be able 
to change the laziness property only before any data has been
written to the stream.  After that, the window is already popped,
and the semantics would get ugly.

In fact, I am very skeptical about the need for an application 
to change laziness at all.  If it can query this property, then
it can just refrain from writing to the steam, if it doesn't want
the window to pop up.

Hence my objection to making the properties variables, not because
of general principal, but because an application could assign to
them at any time.

>===== Original Message From Jay <jayk123 at hotmail.com> =====
>set CM3_ConsoleBehavior=4.1
>m3guiapp
>console behavior still changed
>
>m3guiapp @M3ConsoleBehavior=4.1
>console behavior back to "default"
> - Jay>

Rodney Bates
Retired assistant professor
Computer Science