---- START NEW MESSAGE --- Received: from cherry.ease.lsoft.com [209.119.0.109] by dpmail10.doteasy.com with ESMTP (SMTPD32-8.05) id AC13306A0038; Thu, 29 Jan 2004 05:35:15 -0800 Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <23.00CC29FD@cherry.ease.lsoft.com>; Thu, 29 Jan 2004 8:35:06 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8e) with spool id 3235 for PICLIST@MITVMA.MIT.EDU; Thu, 29 Jan 2004 08:35:00 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 9511; Thu, 29 Jan 2004 08:34:10 -0500 Received: from smtp-out5.xs4all.nl [194.109.24.6] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with ESMTP ; Thu, 29 Jan 2004 08:34:09 EST X-Comment: mitvma.mit.edu: Mail was sent by smtp-out5.xs4all.nl Received: from PAARD (a213-84-20-53.adsl.xs4all.nl [213.84.20.53]) by smtp-out5.xs4all.nl (8.12.10/8.12.10) with ESMTP id i0TDY7n1034215 for ; Thu, 29 Jan 2004 14:34:12 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Message-ID: <000901c3e66c$9590b110$0b00a8c0@PAARD> Date: Thu, 29 Jan 2004 14:34:07 +0100 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: Wouter van Ooijen Organization: Van Ooijen Technische Informatica Subject: Re: [PIC:] Process To: PICLIST@MITVMA.MIT.EDU In-Reply-To: <5.2.0.9.2.20040129073858.01554480@mail.cedar.net> Precedence: list X-RCPT-TO: Status: U X-UIDL: 371856257 > It's no use arguing high level languages at me, I am > frequently scraping > the last cycle in processor bound routines, and I simply > can't pay that penalty. I don't see why you can't use C for 90% of your code and assembler for the 10% that is time-critical? The best route to quality is (guess where the idea comes from): 1- be consistent 2- know, identify, quantify and attribute (find the root cause of) your problems 3- improve by creating mechanisms that eliminate root causes Remember me ranting about duplicate PIC chip ID's? I sell (among other things) pre-programmed PICs. When someone wants one, I put it in my programmer and press the button to load the code. After accidentally shipping the wrong chip I made sure that the button verifies that the correct chip is in the programmer. One more root cause eliminated. Wouter van Ooijen -- ------------------------------------------- Van Ooijen Technische Informatica: www.voti.nl consultancy, development, PICmicro products -- http://www.piclist.com hint: The PICList is archived three different ways. See http://www.piclist.com/#archives for details. .