Valid characters for environment variables across operating systems
While trying to create a reliable application configuration strategy for different applications based on system properties and environment variables I asked myself whether there are known characters and special chars that work across all operating systems. For example on my Mac OS X dots cannot be easily used in environment variables because setting them the way I set other environment variables was not possible inside my .profile file: # configuration for myapp grails.myapp.config=/some/directory/and/file.groovy; export grails.myapp.config As far as I know usually environment variables have a key with uppercase letters and the underscore in it. Is there a known subset of all characters that I can use across all common operating systems?
I looked at the Open Group/POSIX standards site to see what they say. Their XCU specification calls for support of uppercase letters, digits, and underscores (so what you anticipated plus the digits 0-9). At least it's a referenceable standard.
Paranoia 101: use ASCII letter characters and underscores only. Generally upper and lower case letters are legal, but convention dictates using upper case letters.
How the Scheduler decides about the time for the time-quantum in RoundRobin Scheduling Algorithm?
interrupt handler from scratch [closed]
What exactly happens in a power-fail interrupt?
creating task inside other task in freertos
Three threads one for input from keyboard second for encryption and third to print the input
what should i study to get an indepth understanding of operating systems
I am getting the following error after installing Pint-OS and trying to run multiple alarm. I am using bochs as emulator. Any possible work around?
implementation of a simulated disk for an instructional operating system?
rust calling failure::fail_bounds_check with no-landing-pads flag enabled
Is running Docker on bare metal maintainable?
How does a bootstrap program do dual booting of OS
In user-mode, an application will never know what physical address its memory is at, then why does the linker give physical addresses to all sections?
Ones-compliment or sign-magnitude integer representation platform?
How are the code, the hardware, and the OS related? [closed]
dynamic linking v/s dynamic loading
Preemptive Kernel Design