From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: border1.nntp.dca3.giganews.com!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!goblin1!goblin.stu.neva.ru!news.panservice.it!feed.xsnews.nl!border01.ams.xsnews.nl!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Thu, 22 Aug 2013 23:12:22 +0200 From: Georg Bauhaus User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: RTS graph and "temporal formulas" References: <87mwoastdi.fsf@nl106-137-194.student.uu.se> <9d7e5c6c-aeb9-4ac1-a7b0-c048061ae4c6@googlegroups.com> <87zjsar72v.fsf@nl106-137-194.student.uu.se> <2860f114-06c4-42a3-80ac-1c24b631b135@googlegroups.com> <5215d0f8$0$9508$9b4e6d93@newsspool1.arcor-online.net> <52165997$0$9514$9b4e6d93@newsspool1.arcor-online.net> <47123306-9103-47f5-ba6e-5d942bf557d7@googlegroups.com> In-Reply-To: <47123306-9103-47f5-ba6e-5d942bf557d7@googlegroups.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <52167eb8$0$9504$9b4e6d93@newsspool1.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 22 Aug 2013 23:12:24 CEST NNTP-Posting-Host: 648d1863.newsspool1.arcor-online.net X-Trace: DXC=B=]6; DJZ0?:=FQB?mjjV50ic==]BZ:af>4Fo<]lROoR1nkgeX?EC@@0>UoMUM1ISk?nc\616M64>:Lh>_cHTX3j=d?C:Iea7C`0 X-Complaints-To: usenet-abuse@arcor.de X-Original-Bytes: 2749 Xref: number.nntp.dca.giganews.com comp.lang.ada:183108 Date: 2013-08-22T23:12:24+02:00 List-Id: On 22.08.13 20:56, Adam Beneschan wrote: > On Thursday, August 22, 2013 11:34:06 AM UTC-7, Georg Bauhaus wrote: > >> Programmers should not find it confusing, then. They are used to overloading. > > Well, yeah, but mostly overloading on caffeine and extra work. :) +1. (Oh, wait, +1 . No. +1! Ouch. ++1 Nah. +1? Argh! +1,!!! +1,!!! +1 AHA!) (*) (Our espresso machine is simple but g- g- good.) > But I don't know why you think a CAPS LOCK key could be dispensed with in "programmer mode". Using all-caps for constant names is a convention in lots of programming languages. We'd have to know whether or not programmers are actually using CAPS LOCK for (frequently?) typing words in all upper case---I'm still thinking that many use M-U (Emacs), or ~ (vi), or Ctl-Shift-X (Eclipse), or Ctl-Shift-U (VS), ... And that's just typing them for the first time, since language sensitive editing puts the words in context menus near the cursor, ready for automatic placement. (Also, Unix workstations' key mappings frequently had bindings for CAPS LOCK that made the function disappear, IIRC.) __ (*) printf("%d\n", );