Passive versus active translators

2001-06-21 Thread Neal H Walfield
Using settrans to start an active translators sets up a completely different enviornment than that created when a file system launches a passive translator. There are three main differences: o File descriptors - settrans: stderr is the user's tty - libfshe

Re: Passive versus active translators

2001-06-21 Thread Neal H Walfield
My point is that whether a translator is started by the filesystem or by settrans, the behavior should be basically the same. > > o Current working directory > > - settrans: user's current working directory > > - libfshelp: the directory in which we find the > >

Re: "" as target of symlink kills translator

2001-06-21 Thread Neal H Walfield
On Thu, Jun 21, 2001 at 09:45:04PM -0400, Roland McGrath wrote: > > neal@desdemona:~/foo (0)$ ls "" > > ls: : No such file or directory > > Please look into this. Your other tests are consistent with everything > else being correct and this being wrong. Does it make it as far as > diskfs_S_dir_

Re: "" as target of symlink kills translator

2001-06-21 Thread Roland McGrath
> neal@desdemona:~/foo (0)$ ls "" > ls: : No such file or directory Please look into this. Your other tests are consistent with everything else being correct and this being wrong. Does it make it as far as diskfs_S_dir_lookup? ___ Bug-hurd mailing li

Re: "" as target of symlink kills translator

2001-06-21 Thread Neal H Walfield
> Please show test cases that clearly exercise the > particular Hurd RPCs and clearly show the results. You didn't show > e.g. `ls -l ""' in isolation, or `ls -Ll foo'. > > You also haven't tested half the code, i.e. "ls -l foo/a" and the like. neal@desdemona:~/foo (0)$ ls "" ls: : No such file

Re: "" as target of symlink kills translator

2001-06-21 Thread Roland McGrath
> > How about this version? I don't like the looking up "." paradigm. > > It still does not working: `ls foo' fails as this log shows: Now you are talking about the behavior of ls, not of particular Hurd protocols. > neal@desdemona:~/foo (0)$ ls foo > ls: : No such file or directory What "ls

Re: continuing documentation

2001-06-21 Thread Bill White
It doesn't support texinfo. This is an advantage to my way of thinking, but you have your own requirements. I don't know what you mean by "bidirectional pasting of docs into source comments. You put the docs into your source comments, and doxygen pulls them out. You can put quite complex marku

Re: "" as target of symlink kills translator

2001-06-21 Thread Neal H Walfield
> How about this version? I don't like the looking up "." paradigm. It still does not working: `ls foo' fails as this log shows: neal@desdemona:~/foo (0)$ ls -l total 0 -rw-r--r--1 neal neal0 Jun 20 22:44 a -rw-r--r--1 neal neal0 Jun 20 22:44 b -rw-r--r--

Re: continuing documentation

2001-06-21 Thread OKUJI Yoshinori
From: Gordon Matzigkeit <[EMAIL PROTECTED]> Subject: Re: continuing documentation Date: 21 Jun 2001 16:24:02 -0600 > When a `@deftypefun ...' declaration is found, your tool is to compare > the rendered text and prototypes. If there are differences, it should > ask for human intervention to merg

Re: Passive versus active translators

2001-06-21 Thread Igor Khavkine
On Thu, Jun 21, 2001 at 06:01:00PM -0500, Neal H Walfield wrote: > Using settrans to start an active translators sets up a completely > different enviornment than that created when a file system launches a > passive translator. There are three main differences: > > o File descriptors >

Re: continuing documentation

2001-06-21 Thread Roland McGrath
I think Ulrich has a script he uses to keep track of functions missing from the libc manual. It might do part of what you want, and the synthesis of the two is probably a tool of use to at least libc and hurd, and probably other projects too. I am against actual automated generation of the docum

Re: continuing documentation

2001-06-21 Thread Gordon Matzigkeit
> OKUJI Yoshinori writes: OY> If you provide me a specification which satifies your OY> requirement, I may implement such a tool. That would be a quite OY> easy task. ;) If you want it, and think it would be fun, I will not stop you. :) I went through the Hurd header files and took a bun

Passive versus active translators

2001-06-21 Thread Neal H Walfield
Using settrans to start an active translators sets up a completely different enviornment than that created when a file system launches a passive translator. There are three main differences: o File descriptors - settrans: stderr is the user's tty - libfshe

Re: continuing documentation

2001-06-21 Thread OKUJI Yoshinori
From: Gordon Matzigkeit <[EMAIL PROTECTED]> Subject: Re: continuing documentation Date: 21 Jun 2001 15:09:27 -0600 > When I looked at it, doxygen didn't support bidirectional pasting of > docs into source comments, nor did it support Texinfo. If you provide me a specification which satifies your

Re: continuing documentation

2001-06-21 Thread Gordon Matzigkeit
> Bill White writes: BW> Have you looked at doxygen? It lets you put things in the code BW> or out of it. I'm using it for my current project at my work, in BW> a design of a symbol table, and I think it's very useful. When I looked at it, doxygen didn't support bidirectional pasting of

RE: continuing documentation

2001-06-21 Thread Chen Shapira
> Hi, > I think this is a good idea, but I could be usefull a > tool which can parse some code comment and put out docs about > code and relations btw different source file. The output > could be html or sgml (which can be translater in different > format easly). A similar thing I saw i

Re: continuing documentation

2001-06-21 Thread Bill White
Have you looked at doxygen? It lets you put things in the code or out of it. I'm using it for my current project at my work, in a design of a symbol table, and I think it's very useful. On Thu, Jun 21, 2001 at 10:11:10AM -0400, Maurizio Boriani wrote: > -- On 18 Jun 2001 10:34:48 -0600 Gordon M

Re: continuing documentation

2001-06-21 Thread Maurizio Boriani
-- On 18 Jun 2001 10:34:48 -0600 Gordon Matzigkeit wrote -- > I looked at automatic tools for doing this kind of thing, but they all > failed to provide ways of working around text in the generated output. > I wouldn't want to put all the text into the header files. > > My latest direction has b

Re: Internal libc lock interface

2001-06-21 Thread Roland McGrath
> I also found a stub in sysdes/generic for machine-lock.h. It defines > the atomic __spin_lock operations and there are non stub implementations > for severa arch's. It contains very few definitions. So I think I'll > add more definitions and use __spin_lock's throughout pthreads. You should pro

Re: Internal libc lock interface

2001-06-21 Thread Igor Khavkine
On Thu, Jun 21, 2001 at 06:32:12AM -0400, Roland McGrath wrote: > rwlock is to mutex as pthread_rwlock is to pthread_mutex I see. It's just a simple abstraction for the Readers-Writers problem. I also found a stub in sysdes/generic for machine-lock.h. It defines the atomic __spin_lock operations

Re: Internal libc lock interface

2001-06-21 Thread Roland McGrath
rwlock is to mutex as pthread_rwlock is to pthread_mutex ___ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd

Re: GCC-3.0 uploaded to incoming

2001-06-21 Thread Marcus Brinkmann
On Thu, Jun 21, 2001 at 01:11:18AM -0700, Jeff Bailey wrote: > On Thu, Jun 21, 2001 at 09:51:15AM +, Maurizio Boriani wrote: > > > I tried build a cross-compiler environment on Linux Vs. HURD using > > this release of gcc but it did't like work. Today I'll redo > > operations and if you like

Re: Internal libc lock interface

2001-06-21 Thread Marcus Brinkmann
On Thu, Jun 21, 2001 at 01:56:28AM -0400, Igor Khavkine wrote: > In the former case, how do I deal with > rwlocks (what are these btw?) A read write lock is like a file lock with LOCK_SH and LOCK_EX. Acquiring the reader lock locks out writers, and acquiring the writer lock locks out everybody.

Re: "" as target of symlink kills translator

2001-06-21 Thread Marcus Brinkmann
On Wed, Jun 20, 2001 at 11:15:38PM -0500, Neal H Walfield wrote: > neal@desdemona:~/foo (0)$ ls -l foo > lrwxr-xr-x1 neal neal0 Jun 20 22:44 foo -> > neal@desdemona:~/foo (0)$ ls -l foo/ > total 0 > -rw-r--r--1 neal neal0 Jun 2

Re: Annoying free inode warnings

2001-06-21 Thread Roland McGrath
I don't know what the reason really was for that code in the first place (Miles wrote it). I suspect it was just transcribed from ufs. In the ufs format it is improper for the block count to be nonzero in a free inode. For ext2fs, the observed behavior of the Linux kernel is all we have to const

Re: GCC-3.0 uploaded to incoming

2001-06-21 Thread Jeff Bailey
On Thu, Jun 21, 2001 at 09:51:15AM +, Maurizio Boriani wrote: > I tried build a cross-compiler environment on Linux Vs. HURD using > this release of gcc but it did't like work. Today I'll redo > operations and if you like I'll send you make output. I wouldn't expect make-cross to work at all

Re: GCC-3.0 uploaded to incoming

2001-06-21 Thread Maurizio Boriani
On Wed, Jun 20, 2001 at 04:19:49PM -0700, Jeff Bailey wrote: > I have uploaded gcc-3.0 to incoming. > > Thanks to: > Mark Kettenis - Getting the Hurd port updated upstream so we could compile > Marcus Brinkman - Putting up with my ranting. > Matthew Klose - For being very agreeable to patches

Re: Annoying free inode warnings

2001-06-21 Thread Maurizio Boriani
On Wed, Jun 20, 2001 at 11:11:46AM -0700, Jeff Bailey wrote: > Roland, et al., > > Would you accept a patch to add a configure option that removes the > annoying 'free inode' warning messages? I can set it on by default, > if you'd like. > > My final preference would be to leave it disabled unt