Posted in Uncategorized on July 25th, 2008 Comments Off
I just committed the large giant change to bring down elsa’s namespace pollution to reasonable levels. Elsa code now is now using std::foo style, or using namespace std. As I mentioned before, Elsa’s string is now sm::string, a summary of how to perform similar renames is here. The good news is that Pork will soon [...]
Posted in Uncategorized on July 22nd, 2008 Comments Off
I wrote a class renamer and used it to fix my pork pet-pieve #1: a class named string that isn’t std::string. This has been a low priority goal for as long as I’ve been using Elsa. It’s pretty cool to apply a tool to fix itself. The renamer is a 3x simpler than the next [...]
Posted in pork on July 18th, 2008 4 Comments »
It seems that there is some confusion as to what pork is and how it’s related to oink and elsa. So here is my view of it. Pork is my set of tools that use Elsa to rewrite sourcecode (mainly Mozilla code). Our use of Pork is solely for rewriting as it is not suited [...]
Posted in Uncategorized on July 9th, 2008 2 Comments »
Hydras I am close to landing a flow check. Turns out, it is super-easy to introduce new analyses into Mozilla due to a very nice build system hooks setup by bsmedberg. Since coming back from the GCC summit I have forward-ported our GCC patches to GCC trunk. The FSF legal paperwork came through today so [...]
Posted in Uncategorized on July 8th, 2008 10 Comments »
Dear lazyweb, Please explain to me why the following code works the way it does. From looking at the following code and stringstream::str(), stringstream::str(string) docs the behavior of the following code does not make sense to me. #include <sstream> #include <iostream> using namespace std; int main(int argc, char**) { stringstream ss(“foo”); cout << ss.str() << [...]