Ready to be published? LXer is read by around 350,000 individuals each month, and is an excellent place for you to publish your ideas, thoughts, reviews, complaints, etc. Do you have something to say to the Linux community?
I have written on other occasions, you can learn more seeing errors others commit, whatever their cause, which can be more instructive than simply spelling out how to do it correctly. It simply might be the relief of not finding oneself trapped in the same predicament that makes the lesson more likely to stick. This time it was the try / catch code syntax that trapped me. It seemed too transparent and too easily understood, which resulted in my missing a critical aspect. That is today's topic of discussion.
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help