events and drawing to the screen to be handled separately in a goroutine
and input in another.
Amusingly, the closest date I could find for the initial release of curses
was "around 1980" which makes me only slightly older than the library. ;)
On Saturday, 16 November 2013 14:49:54 UTC-8, RickyS wrote:
What could you do concurrently or in parallel, since the codebase is still
'single-threaded'?
That is, could curses start prompting the user for input while it draws
the screen? Or something?
I would guess there is nothing you could do that was correct and reliable.
In my memory the old thing would have to wait until the i/o was done,
anyway.
Perhaps you could reject any call that was not from the starting thread?
I guess the best is provide help for item 2).
Are there startups basing their product on ncurses?
It was designed originally for the vt100, hardware from 30 years ago. The
software is older than you (probably) are.
Best of luck.
--What could you do concurrently or in parallel, since the codebase is still
'single-threaded'?
That is, could curses start prompting the user for input while it draws
the screen? Or something?
I would guess there is nothing you could do that was correct and reliable.
In my memory the old thing would have to wait until the i/o was done,
anyway.
Perhaps you could reject any call that was not from the starting thread?
I guess the best is provide help for item 2).
Are there startups basing their product on ncurses?
It was designed originally for the vt100, hardware from 30 years ago. The
software is older than you (probably) are.
Best of luck.
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
