Sorry for the confusion. I did not realize I was referring to a directed message. I will let Andrey speak for himself.
Regardless of his response, there are numerous papers that point of the failures of ‘errno’ vs exceptions (although Go remediates some of that through the use of multiple return values). > On Jun 29, 2019, at 7:00 PM, Dan Kortschak <d...@kortschak.io> wrote: > > This? > >> the battle you're fighting has already been lost. if you want java >> you know where to find it :) > > I don't see any indication of superiority there. > > You read superiority because you believe it's superior. Not everyone > agrees. Many see a nightmare. > > On Sat, 2019-06-29 at 18:27 -0500, Robert Engels wrote: >> It was certainly implied given the context - Java’s superior error >> handling will not make it to Go (for a variety of reasons), so if you >> want it, use Java. >> >> Oh, and his reply pretty much backs my analysis :) >> >> >>> On Jun 29, 2019, at 6:25 PM, Dan Kortschak <d...@kortschak.io> >>> wrote: >>> >>> That's not what Andrey wrote; he said if you want java error >>> handling >>> us java. No where in his post was any explicit value judgement on >>> the >>> approach. >>> >>>> On Sat, 2019-06-29 at 15:41 -0500, Robert Engels wrote: >>>> And Go has advantages over in many areas so stating “if you want >>>> decent error handling use Java” makes my case quite nicely. >> >> > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/F070A1B1-006D-4CB7-89D8-618868951C6D%40ix.netcom.com. For more options, visit https://groups.google.com/d/optout.
