Hey #cpp, how would you refactor the code in the picture without changing its behavior?pic.twitter.com/1t982nmEsB
I'm worried that the baby thinks people can't change.
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Add this Tweet to your website by copying the code below. Learn more
Add this video to your website by copying the code below. Learn more
By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.
| Country | Code | For customers of |
|---|---|---|
| United States | 40404 | (any) |
| Canada | 21212 | (any) |
| United Kingdom | 86444 | Vodafone, Orange, 3, O2 |
| Brazil | 40404 | Nextel, TIM |
| Haiti | 40404 | Digicel, Voila |
| Ireland | 51210 | Vodafone, O2 |
| India | 53000 | Bharti Airtel, Videocon, Reliance |
| Indonesia | 89887 | AXIS, 3, Telkomsel, Indosat, XL Axiata |
| Italy | 4880804 | Wind |
| 3424486444 | Vodafone | |
| » See SMS short codes for other countries | ||
This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.
Hover over the profile pic and click the Following button to unfollow any account.
When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.
The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.
Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.
Get instant insight into what people are talking about now.
Follow more accounts to get instant updates about topics you care about.
See the latest conversations about any topic instantly.
Catch up instantly on the best stories happening as they unfold.
Hey #cpp, how would you refactor the code in the picture without changing its behavior?pic.twitter.com/1t982nmEsB
I never do return values as errors, I always use error on handle. Much more flexible, unlikely to cause resource errors, much easier for calling code to use:https://godbolt.org/z/6e7q9TPvE
How do you best handle libraries then that do return errors?
Even an I-make-my-own-pasta man like yourself sometimes needs to go out and buy off the shelf (when nobody's looking)? Or at least have to rummage through somebody else's fridge every now and then?
In the rare case where I use a library, I typically isolate that library to one or two actual calls that I write that do whatever it is the library does and keeps it easily removable from the codebase. So I would just put the error-on-handle there.
Usually that is not even necessary, though, because the wrapper code typically wraps the entire operation of the library. I don't generally allow libraries to be integrated into my codebases to the extent where my code is ever actually "using" the library directly.
Gotcha. For my embedded work it's common practice to use a preexisting RTOS. And network stack. But I guess separating the application call from those direct calls can be somewhat abstracted.
Well it's also sort of the wrong question to ask. The original question was "how should I design error handling". And the answer is, the code that has the errors implements it as error-on-handle. So the answer is for the library vendor, not the user.
If the question is, "how do I work around bad error handling decisions in code I didn't write", you really only have two options: wrap it and provide the correct error semantics, or use a different library by better designers :P
With you on that. I just have to suck it up for the projects that are mission critical as all the libraries come with homologation papers. No way around that.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.