Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-WM-Posted-At: avacado.atomice.net; Thu, 6 Jun 02 00:05:53 +0100 Message-ID: <012101c20ce5$8ad627d0$0100a8c0@advent02> From: "Chris January" To: References: <021301c20c92$7c0c61e0$6132bc3e AT BABEL> <20020605151114 DOT GG15167 AT redhat DOT com> Subject: Re: /proc/registry issues Date: Thu, 6 Jun 2002 00:05:53 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 > >Some more or less minor issues w/ /proc/registry: > > > >*) All the files have a size of 0, regardless of their contents. (This might > >explain why if you open a registry file in XEmacs, it comes up empty.) You > >can get the size of a value's data is accessible, without retrieving the > >data itself, via RegQueryValueEx. > > This is similar to most of the files in /proc on linux. This is for a number of reasons, not least the fact that for many files the file size changes quite frequently. Also, for some files, to find the file size you actually have to generate the file's content and that incurs some overhead. Having said that, there's certainly no reason why calling fstat on the files in /proc/registry returns 0 other than the fact that I never got round to writing the code to fill in this information. Also, since I moved the code that generates the file data for the files in /proc to a separate virtual class member, it should be possible to return file sizes for the other files in /proc (however this will incur the overhead discussed above). In my opinion, however, that overhead is unacceptable for a simple file listing and should be avoided. Regards Chris -- 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/