On 07/15/2010 04:21 PM, Hans-Christoph Steiner wrote:

> 
> The options are wait forever or have a timeout.  The vwait code provides
> a timeout.  I am fine with having a long timeout for the conditions you
> describe but it would be harmful to not have a timeout because then
> you'll have a pd-gui process that is just sitting there waiting forever
> for pd to show up whether or not if ever will.  As some point pd-gui
> should tell you that its not likely to happen and just quit.

my approrach was not to wait at all, and as soon as pd shows up
dynamically incorporate the info.
no timeout, no waiting, no deadlock no racecondition.

> 
> For this reason, I think its a bad idea to get rid of the vwait code and
> move stuff to pdtk_pd_startup.  If there are bugs with the vwait
> approach, I'd be happy to fix them.  For what IOhannes describes here,
> it sounds like the timeout just needs to be increased.  Perhaps there

i experienced a race-condition! please do not fix race-conditions by
increasing a timeout.

fgmar
IOhannes

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Pd-dev mailing list
Pd-dev@iem.at
http://lists.puredata.info/listinfo/pd-dev

Reply via email to