>>763
>The suckless fag inside me wants to spill your guts out.
S-s-sorry, Anon-kun ;_;
>>764
>What features are you planning in it that justifies all of it?
I'm not sure if this is a justification, but I'm going for flexibility, which means a hell of a lot of boilerplate.
For example, I didn't want to put a hard limit on how long a string literal could be,
but of course, C doesn't exactly lend itself well to dynamic allocation, and there's no way in
hell I'm copy-pasting realloc() code all over the place.
So now, when the parser encounters a string literal, it just takes small chunks of it and "writes" them to a stream, like this:
writestream(output_stream, chunk_start, chunk_size);
The output stream buffers it using the magic and wonders of malloc() and logarithms,
then once it has the whole literal, it just reads it back out like this:
char *string_literal;
size_t new_size;
getstreamdata(&string_literal, &new_size, output_stream);