| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
| |
Closes #4
|
| | |
|
| |
|
|
|
|
| |
https://panopto.imperial.ac.uk/Panopto/Pages/Viewer.aspx?id=653bf926-6acd-450f-991a-9cdbdf270852
https://panopto.imperial.ac.uk/Panopto/Pages/Viewer.aspx?id=fefdb6bc-4205-4113-bf3b-76ecefc201f2
https://panopto.imperial.ac.uk/Panopto/Pages/Viewer.aspx?id=c4966c37-effd-48f7-b5b9-ebdc5a30b2de
|
| | |
|
| |
|
| |
Fixed #17 : Update for new deadline.
|
| |
|
|
| |
not covered as part of the spec.
|
| | |
|
| |
|
| |
Explanation of why getter/setter methods are used for the PC.
|
| |
|
|
| |
Really stupid typo in the guidance on mem_read_write at the bottom of this page.
The example in the actual documentation is correct though.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
sizes are involved.
|
| |
|
|
| |
Manual merge of changes from pull request by p--b.
|
| |
|
| |
Realised I've been accidentally putting latex quotes everywhere, looks a bit odd.
|
| |
|
| |
Fixed #12 : Ambiguity in include paths.
|
| |\
| |
| |
| | |
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.
|
| | |
|
| |
|
