1) is
probably a more pragmatic approach that doesn't require any code to be
changed and still covers all Pd objects _and_ externals that employ
'post'.
I mean, it's probably fine for display purposes, but the help file
should clearly state:
"do NOT parse the textual content of error message. EVER. SERIOUSLY"
Parsing error messages is like a house of cards that can collapse anytime.
Christof
On 14.06.2021 16:50, Roman Haefeli wrote:
On Mon, 2021-06-14 at 16:11 +0200, Christof Ressi wrote:
Ok, I think we have to seperate two things:
1) posting error messages
2) obtaining error codes
I think Roman is primarly interested in 2),
and 1), I guess...
so that his patches can programmatically deal with certain error
conditions.
Exactly.
While I fully follow your reasoning how 2) is the cleaner and more
correct long-term solution (a real error handling facility), 1) is
probably a more pragmatic approach that doesn't require any code to be
changed and still covers all Pd objects _and_ externals that employ
'post'.
So, I'm not going to argue against 1). If iemguts or Pd would provide
something like IOhannes' [canvaserror], I'd totally use it.
Roman
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
