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,878f0988ded38f50,start
X-Google-Attributes: gid103376,public
From: "Marc A. Criley" <marc.a.criley@lmco.com>
Subject: Passing Time via RCI
Date: 1998/02/02
Message-ID: <34D5D42A.35C7@lmco.com>#1/1
X-Deja-AN: 321362490
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Organization: Lockheed Martin M&DS
Newsgroups: comp.lang.ada
Date: 1998-02-02T00:00:00+00:00
List-Id: <comp.lang.ada>


I would like to pass an entity representing time across an RCI
interface, therefore I need a time type acceptable to the
constraints imposed on RCI units.

Unless I've overlooked something, neither Calendar or Ada.Real_Time,
both being "normal" packages, meet those constraints, and are
therefore unsuitable as providers of the time type.

Do I have to define my own time type?  And write my own time
utilities?  Or do an Unchecked_Conversion from Time to some byte
array I define, pass it, then convert it back?

This seems, uh, silly.  What am I missing?


-- 
Marc A. Criley
Chief Software Architect
Lockheed Martin ATWCS
marc.a.criley@lmco.com
(610) 354-7861