On Dec 20, 2007 1:32 PM, Charles Henry <
czhenry@gmail.com> wrote:
On 12/20/07, Mike McGonagle <
mjmogo@gmail.com> wrote:
> I agree with this. This is just one of the few (or more) things you need to
> know about when dealing with PD. It even says it on the help page for
> [until]...
>
> I don't think I want the software to try and second guess what I want, and
> if I construct an [until] that is an infinite loop, then so be it...
development environments. If you create a problem in your code, you
shouldn't be able to crash the development environment. You halt the
process, make changes, and re-compile.
Well, that is all fine and dandy, but how many other development environments are REALTIME processors? I would love to see Eclipse present the same sort of REALTIME environment, and NOT have it crash when a user wants to do something like this.
The real power in this sort of thing is that YOU CAN do anything you want with it, and in order to keep it general enough AND REALTIME, things like this will happen.
And Pd patching is different from this. I'd say it warrants some
consideration whether there is a means to allow Pd to make errors
without crashing or becoming unresponsive.
And to do this, how much of the realtime stuff would get impaired? There are going to be trade offs in any configuration, and I think the current implementation of [until] is correct in allowing the user to cut off their own legs...
Besides, we all need a coffee break now and then, and a reboot makes those things possible...
Mike