Newsgroups: comp.os.plan9 From: suzuki@granite.cias.osakafu-u.ac.jp Subject: [9fans] Calc2 Reply-To: 9fans@cse.psu.edu Organization: Plan 9 mailing list Date: Mon, 9 Jul 2001 19:46:41 JST Hi, I rewrited my gui calculator program with Control library. This program is in our website: http://basalt.cias.osakafu-u.ac.jp/plan9/s41.html Feature : Calc2 makes connection with bc. Calc2 is implimented by Control and Win librarys. Win (win.h,win.c) is simple gui library, which provides a automatic resizing control. Calc2 has my modified Control "textbutton3", which allows 3 mouse buttons to access. Calc2 has menubar and dialogbox modules made by Control and Win library. BUG : If you resize the window while a dialogbox is opening, it's broken. Thank you. Yoshitatu Suzuki Newsgroups: comp.os.plan9 From: "Douglas A. Gwyn" Subject: Re: [9fans] thread Organization: Excite@Home - The Leader in Broadband http://home.com/faster Date: Mon, 9 Jul 2001 17:33:03 JST Digby Tarvin wrote: > I was aware that the array type was special in that the application of > the '&' operator to it resulted in a change of type but not of value. ? One cannot (meaningfully) apply & to a type, only to a certain kind of expression. When that expression consists of an identifier that has been declared as an object having array type, then in fact &that_identifier is *not* treated specially, according to the C standard, but rather follows the generic rules for the & operator. What is special is the special rule that the unadorned identifier decays, in most contexts, into a pointer to the first element of the array designated by that identifier; this is closely connected with arrays not being first-class objects in C. It is often convenient, but is not natural. Newsgroups: comp.os.plan9 From: digbyt@acm.org (Digby Tarvin) Subject: Re: [9fans] thread Reply-To: 9fans@cse.psu.edu Organization: Plan 9 mailing list Date: Mon, 9 Jul 2001 21:02:43 JST I think you misunderstand. I was referring to the application of '&' to a variable of array type, not to a type. Applied to an array type, it produces a change of type but no change in value. An unusual case where the '&' operator could be replaced by a cast with no change in semantics. I would say that was special treatment, (resulting from the special treatments of array names) albeit in accordance with the C standard. I think you misunderstand. I was referring to the application of '&' to a variable of array type, not to a type. Applied to an array type, it produces a change of type but no change in value. An unusual case where the '&' operator could be replaced by a cast with no change in semantics. I would say that was special treatment, (resulting from the special treatments of array names) albeit in accordance with the C standard. Regards, DigbyT Douglas A. Gwyn: > Digby Tarvin wrote: > > I was aware that the array type was special in that the application of > > the '&' operator to it resulted in a change of type but not of value. > > ? One cannot (meaningfully) apply & to a type, only to a certain kind > of expression. When that expression consists of an identifier that > has been declared as an object having array type, then in fact > &that_identifier is *not* treated specially, according to the C > standard, but rather follows the generic rules for the & operator. > What is special is the special rule that the unadorned identifier > decays, in most contexts, into a pointer to the first element of the > array designated by that identifier; this is closely connected with > arrays not being first-class objects in C. It is often convenient, > but is not natural. > -- Digby R. S. Tarvin digbyt@acm.org http://www.cthulhu.dircon.co.uk Newsgroups: comp.os.plan9 From: boyd@fr.inter.net (Boyd Roberts) Subject: Re: [9fans] thread Reply-To: 9fans@cse.psu.edu Organization: Plan 9 mailing list Date: Mon, 9 Jul 2001 21:06:13 JST From: "Douglas A. Gwyn" > Digby Tarvin wrote: > > I was aware that the array type was special in that the application of > > the '&' operator to it resulted in a change of type but not of value. > > ? One cannot (meaningfully) apply & to a type, only to a certain kind > of expression. When that expression consists of an identifier that > has been declared as an object having array type, then in fact > &that_identifier is *not* treated specially, according to the C > standard, but rather follows the generic rules for the & operator. the one time illegal &array construct falls out of the history of C. the reason being this is that an array identifier was not an lvalue, but an lvalue-expression. read what dennis has to say at: http://cm.bell-labs.com/cm/cs/who/dmr/chist.html ps. i know doug knows this. pps. there's http://cm.bell-labs.com/cm/cs/who/dmr/cman.pdf too. Newsgroups: comp.os.plan9 From: cross@math.psu.edu (Dan Cross) From: cross@math.psu.edu (Dan Cross) Subject: Re: [9fans] thread Reply-To: 9fans@cse.psu.edu Organization: Mememememememmeme Date: Tue, 10 Jul 2001 02:19:23 JST In article <200107091146.MAA27082@cthulhu.dircon.co.uk> you write: >I think you misunderstand. I was referring to the application of '&' to >a variable of array type, not to a type. Applied to an array type, it ^^ a variable of >produces a change of type but no change in value. Errm, isn't this implementation dependent? >An unusual case >where the '&' operator could be replaced by a cast with no change >in semantics. I would say that was special treatment, (resulting >from the special treatments of array names) albeit in accordance >with the C standard. But the semantics are different, as Dennis pointed out in his post. - Dan C. Newsgroups: comp.os.plan9 From: sah@softcardsystems.com (Sam) Subject: [9fans] craptiva Reply-To: 9fans@cse.psu.edu Organization: Plan 9 mailing list Date: Mon, 9 Jul 2001 01:10:03 JST Heya gang, I've a standalone system running on an ibm craptiva. It runs great without the serial/parallel ports enabled, but that's hardly useful. When I enable the either of the ports from the bios to the default values in /dev/ioalloc, p9 boots normal right up until it's about to start rio, then permanently pauses. Any thoughts as to why this might be occurring? Cheers, Sam Newsgroups: comp.os.plan9 From: cross@math.psu.edu (Dan Cross) Subject: Re: [9fans] Chess program? Reply-To: 9fans@cse.psu.edu Organization: Mememememememmeme Date: Tue, 10 Jul 2001 02:30:18 JST In article <73AFF2EAA018984A902FD5DC7D061CDBC4DF@exchange.nsof.co.il> you write: >Some moves or more complicated then chess moves. Yes, the Salsa comes to mind.... - Dan C. Newsgroups: comp.os.plan9 From: Axel.Belinfante@cs.utwente.nl (Axel Belinfante) Subject: Re: [9fans] nVidia GeForce works? Reply-To: 9fans@cse.psu.edu Organization: Plan 9 mailing list Date: Mon, 9 Jul 2001 19:48:16 JST On Thu, 5 Jul 2001 Nicholas Waples replied: > On Mon, 2 Jul 2001, Axel Belinfante wrote: > > > > I'm wondering if Axel ever solved his problem with the cursor offset. > > > > I did not really solve it; [..] > > In case anyone is interested, I attach my original monitor description > > that triggered the problem. At that time I looked at the driver code, > > and noticed that it does something with the 'ehb' mode setting -- > > without understanding what it did, but wondering whether that's related > > to the problem. > > Yes, it was related. My mistake (my first attempt at vga hell). I was > setting the blanking to cover the full overscan, but used 1 bit from the > old value (which added 64 clocks to ehb, which must have caused the 512 > pixel offset). > > Try http://members.optusnet.com.au/~nwaples/nvidia.c to see if it works > now. I had a quick go with the your monitor definition and it worked for > me, so hopefully.... I saw your message while packing for vacation; I hoped to check your fix before leaving, but did not make it in time. I'll check and let you know when I get back. Thanks for your work! Regards, Axel, Newsgroups: comp.os.plan9 From: schwartz@bio.cse.psu.edu (Scott Schwartz) Subject: Re: [9fans] exportfs Reply-To: 9fans@cse.psu.edu Organization: Plan 9 mailing list Date: Mon, 9 Jul 2001 13:12:21 JST I think something like that is a good idea. The thing that I sometimes want is to do that in the local case, a way to say "everything under /foo is read only", as a sanity check on e.g. a http daemon. Maybe the best approach is an ro-fs that you mount first, and then exportfs? Is that more modular, or just more work? Newsgroups: comp.os.plan9 From: cross@math.psu.edu (Dan Cross) Subject: Re: [9fans] exportfs Reply-To: 9fans@cse.psu.edu Organization: Mememememememmeme Date: Tue, 10 Jul 2001 01:37:36 JST In article <20010709035619.27191.qmail@g.bio.cse.psu.edu> you write: >Maybe the best approach is an ro-fs that you mount first, and then >exportfs? Is that more modular, or just more work? I like that better, because I think it's more generalized, and can thus apply to things other than exportfs, as well (consider what you mentioned about the http server). - Dan C.