W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2011

[Bug 11682] under-specification of func-available-environment-variables and unc-available-environment-variable

From: <bugzilla@jessica.w3.org>
Date: Mon, 17 Jan 2011 18:33:26 +0000
To: public-qt-comments@w3.org
Message-Id: <E1PettO-0003Wm-86@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11682

--- Comment #13 from Liam R E Quin <liam@w3.org> 2011-01-17 18:33:24 UTC ---
Dana, I don't really understand the amount of fuss this has generated.  We did
not put it in the language book. It's in the function library.

However... languages with access to environment variables include...

C (part of the core, required, standard libraru for ANSI and ISO C)
C++ (same)

Scheme (get-environment-variable / getenv didn't make it into R6RS but appears
to have been approved for addition to their next version)

Perl (via a built-in map; it was felt too important to be delegated to the
POSIX module even though that's part of the standard distribution)

Python (via os.environ, a core required module)

Java, via System.getenv()

Scala (not surprising, as it runs on a JVM)

SQL implementations do appear to provide GETENV() even if it's not in any
standard.

There are lots more, of course, but I don't see why I should spend time
demonstrating something to you that you could answer yourself easily with a Web
search.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 17 January 2011 18:33:27 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:45 UTC