I'll be much busier with real life in the coming 6-8 weeks. I believe it 
a good time for a status report.

My initial thought in early April motivated by ingo's meta thread and 
more bug reports, was to re-implement current keywords while generally 
addressing a list of issues rather than continuing to patch bugs, but as 
I got close-ish to that goal early in May, it sank in that for v4 - and 
all I want to try in yuqk - the options themselves must be re-worked 
more or less in total.

SO! I tore down what I'd done and started again. I'm still in refining 
things, but I'm getting closer to what a refined yuqk/V4 option set 
might be.

I've mentioned previously a yuqk goal is to eliminate default{} and 
global_settings{}; pushing those 'options' out of the parser and into
the options parsing and set up module.

As Chris has mentioned elsewhere, a goal for future major revisions is a 
more modular code structure. This itself drives options re-work / changes.

Aiming for utf8 support and moving file I/O to C++17's std::filesystem 
(Initially in just the options tangled code).

Where old option names might be used (and because I'll be suffering with 
these options changes too!) the new module reports errors for each old 
use case with information on what to use instead.

In separate threads to this forum I plan to detail the current option 
grouping changes so folks can think about them as a modules or groupings 
of functionality.

Lastly, if that Grizzly bear kills me during my wrestling match at the 
Alaskan, Heavy Drinking and Betting Club (AHDBC) in July, I'll have, at 
the very least, left some record of my options re-work effort thus far. 


Bill P.

Post a reply to this message