| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\
| |
| |
| | |
Fixed: #13 (C++11)
Fixed: #15 (test name warning)
|
| | |
|
|/ |
|
|
|
| |
Answered a couple of questions I'd received.
|
|
|
|
|
|
| |
which never helps. Changed to be real code.
(Deliberately kept the error checking though).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Note that I would not really consider this as a backwards
compatibility problem, as there is a documented way of
returning error codes, and an error code exists for this
situation. One would expect any reasonable implementation
to check for non-null as a sanity check, as it so cheap.
The exception would be if it was documented as a performance
critical method (which it is, but we don't care about
performance), where you would probably either put a blanket
warning "No pre-conditions will be checked" for the module,
or ideally on just the performance critical functions.
|
|
|
|
|
|
|
| |
I didn't add constraints on the pointer validity, as they are covered
under a more common sense argument. There is no reasonable interpretation
for passing a null or invalid pointer for pc, as it cannot give the
caller any more information than they already have.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixed #4: Yup, you can use C++11 if you want. It's difficult to see what
you would need beyond auto for convenience though.
Fixed #5: I've given examples of compilers that may get used, depending
where I happen to be when I run it. Over-inclusion of headers I'm aware
of, and will fix during compilation. Usually I run it under two platforms
to check they are the same output, and to look for non-det bugs. Anything that is
genuinely a compiler or system bug, I'll just fix. If xcode doesn't
comply with the C/C++ standards then... don't use it.
Fixed #11: dup of 4.
|
|\ |
|
| |
| |
| | |
Fixed #2 : replace <your_login> with [your_login]
|
|/ |
|
|
|
| |
I give up on markdown tables. There is no markdown, there is only Zuul.
|
| |
|
| |
|
|
|
|
| |
it is not.
|
| |
|
|
|