Re: "vim" is for nerds who can get a date.

rbowman wrote this copyrighted missive and expects royalties:

On Tue, 16 Apr 2024 18:07:23 -0400, Chris Ahlstrom wrote:
>
>

I dunno, I have a MIDI conversion project I extended that created the
parser using flex.
 
I run "info flex" and I shudder.

>
Don't forget it's running mate, bison. There was a theory the support
people needed a way to configure simple text reports to display incident
information. The programmer used flex and bison to create a configuration
language plus a 20 page document on its use that nobody understood. To
further obfuscate the matter the executable used macros like
>
#define CREATE_FMT_STR_DECL(obj) \
char *create_##obj##_fmt_str (fmt_strf_map_t *fmt)
#define CREATE_FMT_STR(obj) \
CREATE_FMT_STR_DECL(obj) \
{ \
return (create_obj_fmt_str (obj##_map, fmt)); \
}
>
to generate code which didn't have much in the way of actual functions. It
was a maintenance nightmare.

For even more macro madness, check out Boost. Luckily, one rarely needed
to read that stuff.

Example configuration files were provided which support used without
understanding them. If a client requested a change in a report the support
people developed a ploy of mangling the example and asking programming if
it was correct in hopes that programming would fix the thing.
>

Isn't Wix like, deprecated? (years ago)

>
Not even a little bit....
>
https://wixtoolset.org/docs/wix3/

Ah, now I remember. Wix was actually on the Navy network blacklist for
some reason. We ended up using NSIS. We had been using InstallShield but
wotta crocka shit!

For my projects that are ported to Windows I use NSIS.

Note that v4 was more or less a breaking change from v3. You can install
the tool in Visual Studio and it will generate templates that may or may
not be useful. It is, as they say, powerful. (translation: it's like
someone gave you a paraglider, an instruction book, pushed you off a
cliff, and yelled 'Good luck!')

--
WinAmp really whips the llama's ass!