- Mar 19, 2015
-
-
Meredith L. Patterson authored
Wrote __call metamethod for HParsedToken, so now returning proper Lua types out of tokens, though char is still an issue.
-
Meredith L. Patterson authored
-
- Mar 18, 2015
-
-
Meredith L. Patterson authored
-
Meredith L. Patterson authored
HCountedArray now looking slightly more table-shaped thanks to __call. Will need to do something similar for HParsedToken to return the appropriate Lua type based on its type tag.
-
- Mar 17, 2015
-
-
Meredith L. Patterson authored
-
Meredith L. Patterson authored
-
Meredith L. Patterson authored
-
Meredith L. Patterson authored
-
Meredith L. Patterson authored
-
Meredith L. Patterson authored
-
Meredith L. Patterson authored
-
- Mar 04, 2015
-
-
Sven M. Hallberg authored
-
Sven M. Hallberg authored
-
- Feb 23, 2015
-
-
Sven M. Hallberg authored
-
- Feb 12, 2015
-
-
Sven M. Hallberg authored
-
- Jan 30, 2015
-
-
Sven M. Hallberg authored
-
Sven M. Hallberg authored
-
Sven M. Hallberg authored
-
Sven M. Hallberg authored
-
- Jan 23, 2015
-
-
Sven M. Hallberg authored
-
Sven M. Hallberg authored
-
- Jan 05, 2015
-
-
Steven Dee authored
-
- Jan 04, 2015
-
-
TQ Hirsch authored
NEWS: * Switching endianness mid-byte no longer potentially re-reads bytes. * bit_offset now consistently refers to the number of bits already read. * HParsedTokens now have a bit_length field; this is a size_t. This may be removed for memory reasons. The bit writer has not yet been updated to match; the result of switching bit writer endianness in the middle of a byte remains undefined.
-
- Jan 03, 2015
-
-
Steven Dee authored
I've found this especially useful in combination with my own _attr_uint_const for things like flags and type specifiers. It's possible that its usefulness might be diminished significantly if there were a built-in bitfield constant parser -- that certainly would eliminate all of my current uses of it -- but it still seems nicely symmetric with H_ACT_APPLY.
-
Steven Dee authored
Tabs after the first non-tab character are crazymaking. I picked 8 because it wasn't 7 and caused the backslashes to line up on H_ACT_APPLY.
-
- Dec 07, 2014
-
-
Steven Dee authored
They apparently removed alloc_size at some point (it was a no-op beforehand), causing the attribute to throw an error when clang compiles anything including allocator.h.
-
Steven Dee authored
It's causing unreferenced-variable warnings, and isn't referenced anywhere aside from benchmark.c. If client code is likely to reference it, perhaps move it into another header, so people who include hammer.h don't have to refer to it to have warning-free code.
-
- Jun 18, 2014
-
-
Sven M. Hallberg authored
-
- May 12, 2014
-
-
Meredith L. Patterson authored
-
Meredith L. Patterson authored
-
- May 11, 2014
-
-
Meredith L. Patterson authored
-
- May 07, 2014
-
-
Sven M. Hallberg authored
-
Sven M. Hallberg authored
-
Sven M. Hallberg authored
-
- Apr 20, 2014
-
-
Meredith L. Patterson authored
-
Meredith L. Patterson authored
-
Meredith L. Patterson authored
-
Meredith L. Patterson authored
-
Meredith L. Patterson authored
-
- Apr 13, 2014
-
-
TQ Hirsch authored
-