Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <402BC0EE.9070203@tlinx.org>
Date: Thu, 12 Feb 2004 10:07:42 -0800
From: linda w <cygwin AT tlinx DOT org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: [Fwd: Bug: Perl:IsWinNT undefined & RFE,  only use "/" in reg values, not names..?]
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

I'm on an NT compatible (Windows XP) release trying to run the reg utils 
but I
get an error message that IsWinNT is not defined, so they the reg utils 
fail to
install.  Presumably IsWinNT is to differentiate between Protected and
DOS-based versions of Windows but presumably wouldn't be defined on OS's 
where
Windows compatibility is not possible or desired.

Since the purpose of Cygwin is to  allow developers to use both the 
Microsoft
Win32 API and/or the Cygwin API to write utils that can be used from 
both the
bash shell and the standard Windows command shell
(http://cygwin.com/faq/faq_1.html, 2nd par.), having Cywin perl 
returning "Not
running on top any version of windows) would seem to be a bug.  Am I, 
perhaps,
doing something else wrong and this feature does work for others?  If 
so, I'll
have to go bury my head for a while under some lines of code.

Speaking of compatibility --  there is only 1 application I know of that 
uses
"/" in keynames -- Cygwin.  Since it's already been noted that this makes it
very awkward to access these keys in /proc, perhaps cygwin could op for 
better
windows compatibility and go with the unofficial custom of not using "/" in
keynames?   Many or most examples I've seen of manipulating the registry 
show
the use of some "change separator" facility and then use "/" as the example
separator in code examples -- as "/" is already the separator in other 
parts of
the OS and "\" is a pain to use since most modern languages use it for
literalizing the next character

What do you think?  Are these fixable/changable?

Thanks,
-linda





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/