Russ Abbott wrote:
I think it would be a very nice feature to be able to declare variables to be data flow variables. But for every variable to be treated this way is quite unintuitive--especially for new Oz programmers.
My opinion is just opposite :-p Having variables being dataflow as a default means that declarative components automatically behave well with concurrency. In fact, if the boundaries of a component are variables, it will behave correctly in the presence of concurrency. Most languages require you to rewrite your program if you want to make it a bit concurrent!
If someone told you, "Try this neat new language," and you typed in what seemed like the simplest of all programs::declare X print X+1and nothing at all happened. Wouldn't you be confused? Perhaps you even intended to type:declare X = 5 print X+1and just forgot the "= 5" part. Wouldn't you expect the language to help you out and wonder why it didn't? No response at all is what you get from a rude clerk when you don't ask for something in exactly the right way.
Someone should fix Ozcar (the debugger). The panels showing variables seem broken. However it still points out the blocking statement in your source file. If those panels were working, you'd have a quick look at them, and "Doh!" ;-)
Cheers, raph _________________________________________________________________________________ mozart-users mailing list [email protected] http://www.mozart-oz.org/mailman/listinfo/mozart-users
