#!/bin/sh pacman -Syu --noconfirm
Since couple of weeks I observed strange behavior of the share function on my Nexus 7: I could not share anything to Gmail, it was just not there.
Well the solution of the problem was just too easy: Reinstall the gmail app over the app store. Voilà, it works again. I’m happy 😉
Since I don’t like the the default parameters of the DIR command in the command line mode, I wandered if there is a way to set it permanently, to avoid typing each time “DIR /O:G/P” for example. And of course there is a way, following step-by-step for XP, but should be kind of similar for other windows versions too:
- Win + Print opens System Properties dialog
- Klick on the Advanced tab
- Environment variables
- Add a new variable with the name DIRCMD and the value(s) you want to be displayed in System variables field.
Informally, exception-safety in a component means that it exhibits reasonable behavior when an exception is thrown during its execution. For most people, the term “reasonable” includes all the usual expectations for error-handling: that resources should not be leaked, and that the program should remain in a well-defined state so that execution can continue. For most components, it also includes the expectation that when an error is encountered, it is reported to the caller.
More formally, we can describe a component as minimally exception-safe if, when exceptions are thrown from within that component, its invariants are intact. At least three different levels of exception-safety can be usefully distinguished. These distinctions can help us to describe and reason about the behavior of large systems.
In a generic component, we usually have an additional expectation of exception-neutrality, which means that exceptions thrown by a component’s type parameters should be propagated, unchanged, to the component’s caller.
From boost c++ libraries