Rodrigo Martins wrote:
> What if instead of changing every program we changed the standard
> library? We could make stdio line buffered by setting an environment
> variable.
I applaude this idea! Environment variables seems to be the right spot
for any config a library could need: are unobstrusive, can be set by the
program calling it, yet keep each program configurable by default.
Markus Wichmann <nullplan_AT_gmx.net> wrote:
> The problem you run into here is that there is less than one standard
> library.
The problem was stated here for libc's stdio, but I still like the idea
for new libraries: A call to getenv (which never fails), into xyz_init().
What about $DISPLAY, $MALLOC_OPTIONS (OpenMacOS™), or $LIBV4LCONTROL_FLAGS[1]
or some LIBXYZ_DEFAULT_DEV_FILE=/dev/xyz3?
Insane and breaking some important concept?
To keep for debugging purposes only?
Not to use for every kind of configuration?
Better let the vibe-coder control the entirety of the library?
Although, if a library (or any program really) does not *require* any
configuration or environment variable and always works without that,
I like it even better.
[1]:
https://dropboxhub.com/philips/libv4l/blob/cdfd29/libv4lconvert/control/libv4lcontrol.c#L369-L371
Received on Mon May 30 2022 - 08:29:17 CEST