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,f84a857bba053719 X-Google-Attributes: gid103376,public From: Matthew Heaney Subject: Re: System.Address_to_Access_Conversions Date: 1998/07/26 Message-ID: #1/1 X-Deja-AN: 374924491 Sender: matt@mheaney.ni.net References: <98071509523514@psavax.pwfl.com> NNTP-Posting-Date: Sat, 25 Jul 1998 17:51:36 PDT Newsgroups: comp.lang.ada Date: 1998-07-26T00:00:00+00:00 List-Id: "Marin David Condic, 561.796.8997, M/S 731-96" writes: > This made tagged records a major nuisance to > me when trying to utilize them in a communications situation where > I wanted to beam the bits down a wire. If something is a "major nuisance" to do, then you should interpret that to mean that you shouldn't be doing it. Do not try to send a tagged type directly across an external interface. You must first convert the object to an external format, preferably using the streams facility and/or the DSA. > There is a way to use streams to get rid of the tag information if > you need to do it, but if you are in some way interested in > utilizing tagged records to overlay physical hardware, etc., you > will find there are no good answers. No good answers, becuase the question itself is all wrong. > If you come across information that suggests a solution to > controlling representation of tagged record types that sounds > standard and portable, I'd be interested in hearing about it. Please don't fight the language, as there are "standard and portable" ways to get the job done. That the representation of a tagged type isn't under programmer control is a feature, not a flaw.