Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sources DOT redhat DOT com
From: "Ronald Landheer" <info AT rlsystems DOT net>
To: "Corinna Vinschen" <cygwin AT cygwin DOT com>
Subject: RE: [PATCH] ls & "magic" cygdrive dir (was: RE: cygdrive stuff)
Date: Mon, 24 Sep 2001 21:24:17 +0200
Message-ID: <NFBBLOMHALONCDMPGBLFEEELCCAA.info@rlsystems.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
In-Reply-To: <20010924141016.Q17037@cygbert.vinschen.de>
Importance: Normal
Content-Transfer-Encoding: 8bit

Corrina said:
> On Mon, Sep 24, 2001 at 01:01:26PM +0200, Ronald Landheer wrote:
>> The only problem I see immediately is a small one: my C++ may be a
>> bit rusty, as I haven't made any code in C++ in at least two years -
>> though I'm quite familiar with the object-oriented model, most of the
>> expressions and I think I might still know how to put a class
>> together.. (but with your code to start out with, I should pick it up
>> quickly enough.. I have C++ on my CV as one of the languages I
> "speak", so I might as well remember it ;)
> Programming in a language is the best approach to get rid of the rust
> ;-)
In deed it is, and as I just accepted a job as a programmer/developer this afternoon (which kinda ends my freelancing days, I guess), which will require me to put a nice new coat of paint on my C++, I'll get the sandpaper out of the toolbox and start :)

>>> I can extract the mount aspects of my current code tonight, and will
>>> send to cygwin-patches (simply FYI). You can then choose whether to
>>> build on that, or start from scratch.
>> If you could Cc it to me: I'm not on the patches list (and seeing as 
>> this is the first time I'm actually going to work on a patch 
>> for Cygwin, 
>> I had no reason to be there before..)
> It makes sense to subscribe to cygwin-patches, cygwin-cvs and
> cygwin-developers when contributing to Cygwin internals.
> However, Chris is a bit handicapped this week so it could take
> a week before he can approve your subscription.
> Another thing is, you will have to sign an assignment form as
> it's described on http://cygwin.com/contrib.html.  Unfortunately
> it has to be send using snail mail...
> I hope that doesn't discourage you.  We would be very glad to have
> another person on board who doesn't chicken out when looking into
> the Cygwin sources ;-)
Whenever I wet my pants, I'll take a shower and put new pants on - but 
chickening out is not my style :)
I assume that subscribing is a matter of sending some E-mails (to 
cygwin-*-subscribe AT cygwin DOT com), so I'll do that.

>>> I think that you'll have some work to implement that due to a
>>> design constraint inside of Cygwin.  In theory the functionality
>>> of stat/readdir etc. has to be moved inside of the fhandlers
>>> first.  While that already works for stat on disk files it's
>>> currently not implemented for readdir at all.
>> What design constraint is that? (What is being constrained, exactly?)
> As I wrote, opendir/readdir/etc. are global implementations
> which only work on disks.  No virtual filesystems (/dev or
> /proc or *cough* /registry) are supported.
Ah, but that's not a design constraint (at least: I wouldn't call it 
that) - that's an unimplemented feature. I thought you meant something 
that couldn't be implemented because Cygwin would croak.. (like using an 
umbrella like a parachute - due to some design constrains on the 
umbrella, that just doesn't work).
Missing features can be added - turning an umbrella into a parachute is 
just not possible, if you want to keep the umbrella-functionality.

Hope I'm not being too cryptic here ;)

Greetz!

Ronald


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/