aboutsummaryrefslogtreecommitdiff
path: root/src/tests/optparser.cpp (unfollow)
AgeCommit message (Collapse)Author
2011-01-20Bu::FString is now String, and there's a shell script to fix any other programsMike Buland
that were using fstring, I hope.
2011-01-19Started work adding more functions to stream, and changing to a new size type.Mike Buland
2011-01-10The FString is much more optimized, and hopefully still works accurately.Mike Buland
2011-01-10Tweaking the fstring, almost done.Mike Buland
2011-01-06This may be about it for updates to core, I can't think of anything else I needMike Buland
to do right now. This commit contains minor fixes to the cache stores so they don't generate any warnings, and the hashtable includes == and != operators now.
2010-12-03Fixed a bug in the csv reader, it would drop the last field in a line if theMike Buland
comma was the last character. It's best to preserve every field, even if it's completely blank.
2010-11-24david - some mix of qt or mingw or something has a min and max macro that ↵David
conflict with this file... #undefed them for now, figure out better solution later
2010-11-19MyriadFs is starting out...but the FUSE system is...akward at best.Mike Buland
2010-11-19Wow, I can't believe I forgot to add myriadfs.Mike Buland
2010-11-19I now think that this may not work out at all. It looks like if we want properMike Buland
Unicode handling we'll need to implement a series of codecs and converters as well as tables of codepages and lookups. It'll be interesting, I guess, but it makes me care a lot less about proper encoding. Anyway, UtfString uses shorts instead of chars, so it's a step in the right direction, but still not enough to be able to handle proper UTF-16 encoding, maybe UCS-2 encoding, but... ...that's lame. Bu::FBasicString has been generalized a bit with optimizations from libc for char based strings. It also, unfortunately, still uses char-only functions in several places, those all rely on char casting strings at the moment just to get the thing to compile. Basically, it's not a good UTF-16 solution yet, and it may never be and remain compatible with char based strings.
2010-11-10Added a couple more debugging functions to Bu::Myriad, and exposed them in theMike Buland
cli tool.
2010-11-04FString tests, the new one causes a segfault with the old fstring.Mike Buland
2010-10-29Minor change, I discovered where it was getting stuck all this time. If theMike Buland
underlying stream hits the end before the end of the bzip2 stream then it just reads forever...that's lame. Now it throws an exception.
2010-10-27Interesting tweak to the variant and optparser classes. In the Variant, itMike Buland
would always fail if a const char * was passed in, it now converts these silently to Bu::FStrings, good to know... Also, the OptParser now uses a Variant for overrides, meaning it doesn't have to do extra parsing, and the amount of code you have to write may be significantly reduced. Pretty sweet, overall. There is one downside. For the moment if you use a non-standard type or object as the target of a parameter it always needs to have a formatter >> operator defined, even if you override and the formatter >> operator is never called. Hopefully we can get around this in the future. Also, it looks like it should be relatively trivial to create conversion functions for the variant, they'll just be global template functions that take two parameters, source type and target type. Should be good times.
2010-10-20Hopefully this fixes some really out there fstring corner casese.Mike Buland
2010-10-18Several of these new files will go away, but I didn't want to lose them for now.Mike Buland
The parser works! The parser compiler works! It makes parsers! Now we just have to implement post processing, token lookup tables, and storage.
2010-10-17Hey! The parser parses now! It's actually a little stupid, I didn't implementMike Buland
lookahead or precedence, but I should be able to do that easily with the next version. I'm treating this more as a proof of concept than a real working model. Although it can handle +, -, (), and = :)
2010-10-16Many, many changes. Documentation changes, renamed the socket class toMike Buland
TcpSocket, fixed many other things, and finally removed ParamProc. Anything that needs it will now have to switch to OptParser.
2010-10-15RingBuffer is now SharedCore. I think that's all the container classes, thereMike Buland
may be a few other things that should change too, we'll see. Played with doxygen docs on List, we can actually use @cond to remove things from the docs, either permenently or conditionally, and so I could trick it into making all of the sharedcore classes inherit from the same SharedCore in the docs instead of different ones. Or, just not inherit from SharedCore at all. What to do...? :-P I also got rid of ListHash, it wasn't working out yet anyway.
2010-10-14SharedCore has more features now, which is cool, including a test to see ifMike Buland
another object of the parent type has the same core, and another to clone the parent object. That one is pretty cool, it means you can now get a real copy when you want to, great for multi-threaded stuff. Also, two more classes are now SharedCore: Hash and Heap!