From mboxrd@z Thu Jan 1 00:00:00 1970 From: perry at piermont.com (Perry E. Metzger) Date: Mon, 9 Jul 2018 07:50:35 -0400 Subject: [COFF] Other OSes? In-Reply-To: <20180709073241.6babe8f4@jabberwock.cb.piermont.com> References: <82df833ae2a587b386b4154fc6051356a3510b19@webmail.yaccman.com> <129a13eb-de93-3d6b-b7b5-d0df13e60c87@spamtrap.tnetconsulting.net> <20180709015650.GA29373@thunk.org> <3bcafd7f-26be-8770-c754-b179e9cff4a5@spamtrap.tnetconsulting.net> <20180709073241.6babe8f4@jabberwock.cb.piermont.com> Message-ID: <20180709075035.59bf47d0@jabberwock.cb.piermont.com> On Mon, 9 Jul 2018 07:32:41 -0400 "Perry E. Metzger" wrote: > On Sun, 8 Jul 2018 21:52:09 -0600 Warner Losh > wrote: > > It would also let the program do 'noise > > words' like TOPS-20 did w/o having to actually parse them... > > Noise words are a thing Unix is missing, but given the lack of > CMND JSYS style completion, the reason for the lack is obvious -- > nothing generates noisewords so nothing needs to ignore them. This > is yet another cool thing clang's --complete hack could make widely > available, though then we'd need a standard for noisewords. Actually, it occurs to me that noisewords aren't actually needed. The printed help during completion can handle conveying the information that noisewords provided. Perry > > clang --complete is an interesting variation on my ideas within > > the realm of doing non-standard weird things and starts to place > > the burden of knowledge on the program itself, which is more in > > line with the thinking of Unix and the main stream of OOish > > thought we've know about since the early 70s with smalltalk and > > other such pioneering things. > > Precisely. The clang hack is exactly what one would want if it could > be made popular. > > Perry -- Perry E. Metzger perry at piermont.com