It behaves like print but instead of just printing the message, it treats all input as an error. On Oct 14, 2015 5:15 PM, "Matt Barber" brbrofsvl@gmail.com wrote:
I think error is in the log library.
Did the license issue with expr ever get sorted? On Oct 14, 2015 4:40 PM, "Jonathan Wilkes" jancsika@yahoo.com wrote:
Hi Matt, Looks like expr has '^'.
What is [error]? Is it in Max?
-Jonathan
On Wednesday, October 14, 2015 2:40 PM, Matt Barber brbrofsvl@gmail.com wrote:
A simpler thing would be to just have any object that deals with file i/o to return something like an "exit status" on a read or after a write attempt.
As long as we're wishing for stuff, I wish vanilla included the [error] object for proper error handling in abstractions. And a bitwise XOR.
On Wed, Oct 14, 2015 at 6:12 AM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
On 2015-10-14 12:07, IOhannes m zmoelnig wrote:
On 2015-10-14 09:34, Roman Haefeli wrote:
I don't see why [textfile] shouldn't report that to the patch instead
of
the console.
because it would require a lot of code to be added to all use-cases of [ŧextfile] in order to not break the feedback where it is indeed desired and needed.
this should have read: "because it would require code to be added to all uses of [ŧextfile] where the error is indeed desired and needed."
this *could* be done in a way satisfying to both, if Pd had some kind of exception handling. however, it doesn't.
fgamsdr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list