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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,67c50b972ca3b532
X-Google-Attributes: gid103376,public
From: tmoran@bix.com
Subject: Re: Realtime Ada Conferences
Date: 1996/03/28
Message-ID: <4jdcfd$7gc@news2.delphi.com>#1/1
X-Deja-AN: 144634310
organization: Delphi Internet Services Corporation
newsgroups: comp.lang.ada
Date: 1996-03-28T00:00:00+00:00
List-Id: <comp.lang.ada>

>Note that these context switch times are for simulated context switching
>(i.e. threads simulation), rather than for use of operating systems
<flame on>
  Is it just me, or does calling this a 'simulated context switch'
remind others of Orwellian language redefinition.  A 'context switch'
means a switch to a different Ada task.  If an implementation wants to
include switching OS threads, or rebooting to a different OS, or
switching to a different computer in orbit on the other side of the
globe, fine, but don't redefine that as a context switch and anything
else as 'simulated'.  Especially in a context discussing whether a
'context switch' takes more than 20 us in a language designed for
embedded systems.
<flame off>