comment on

It makes me rather nervous to see a "systems programming language" of some years gestation that can say "exceptions remain an open issue" and yet doesn't immediately say 'what' their error recovery model is.

If I look at their tutorial it seems to be checking returned error flags and/or results for abnormal conditions. Maybe it's the PBP koolaid but I was convinced manually checking for every possible error condition / combination, and everywhere, was not best practice and not scalable.

My first impression is this is another interesting Google color thrown on the wall to

see if it sticks
see if the art gallery people say 'ooooo!'

So, is this just very early days, or just 'goo'?

In reply to And the bumps in the night? by shenme
in thread Thoughts on "Go"? by punkish

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks