Re: [Bug-gnubg] Re: GNUbgGTK threads

[Joern Thyssen]

On Fri, Jun 28, 2002 at 10:26:31AM +0200, sev_notrump wrote
> 
> ----- Original Message ----- 
> From: "Joern Thyssen" <address@hidden>
> To: "GNU Backgammon Bugs" <address@hidden>
> Cc: <address@hidden>
> Sent: Friday, June 28, 2002 9:46 AM
> Subject: Re: GNUbgGTK threads
> 
> 
> >........................................... The user may initiate an
> > operation via the GUI that will update the same analysis that's running
> > in the background.
> 
> Well if it's that simple just change the above in :
>     "The user may not initiate an
>     operation via the GUI that will update the same analysis that's running
>      in the background."
> 
> 
>      pseudo code for "the play new game option"
> 1:    disable creating new threads                       You can archieve 
> that by disabling menu_entries which are                                      
>                                                   invokin new threads 
> involving  the analyses function
> 
> 2:   disable not relevant threads                           Creates more speed
> 3:   initialise a thread which analyses the
>       previous played move
> 4     play game
>      ......
> 5    if playing done
> 6:       remove the thread created in 3
> 7:       enable not relevant threads                        restore the 
> treads disabled in 2
> 8:       enable creating new threads                      Enable the menu 
> items , disabled in 1

I don't think it's so straight-forward as you make it sound. It's not a
trivial task to ensure that all vital subroutines in gnubg is
thread-safe.

However, it's an interesting idea, but it's not on the top of my TODO
list.

Jørn

-- 
Joern Thyssen, PhD
Vendsysselgade 3, 3., 9000 Aalborg
+45 9813 2791 (private) / +45 2077 2689 (mobile) / +45 9633 7010 (work)