From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 32661 invoked from network); 25 Jan 2021 16:49:36 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 25 Jan 2021 16:49:36 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 4E4B09C7D0; Tue, 26 Jan 2021 02:49:33 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id AAFE79C63D; Tue, 26 Jan 2021 02:49:16 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="cQYt1OHo"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id DF0E29C63D; Tue, 26 Jan 2021 02:49:14 +1000 (AEST) Received: from mail-lj1-f174.google.com (mail-lj1-f174.google.com [209.85.208.174]) by minnie.tuhs.org (Postfix) with ESMTPS id 204A49C5FD for ; Tue, 26 Jan 2021 02:49:14 +1000 (AEST) Received: by mail-lj1-f174.google.com with SMTP id l12so13573737ljc.3 for ; Mon, 25 Jan 2021 08:49:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EGGKNrPOLX/N2gQnpJHvJaZ4GLMl2zV2fBq/6LlBRpI=; b=cQYt1OHo5GT+VtFUUg6TUzWPFiIHUl7ongg5Q9QfYTsOde0DbHW1poaVP7o1tm9CKY vesKNQV1NK8SjgMyA1glCy8H8t5lw3v/dy1RIKoB9sqECWIqI+6AM588QIH8yDhP/feS iWRCd7LTwZ0dxb1wsuQk8LKPCCr7jKMmGVqENIHX2+7sHp3wiw821V4AY6CUTqIyGXMl 6PXGR5jidQiVzuBM5Lv+BKD6E1tGWnsufM41DhPqUGlMMk6+bSBalgGDJr0dj5oWv3XG 8eeWnM8Jnvd85XjnHMmlN2niUkv+Eog3janPtiZcWCLRrAMgMoW0h/GI5/OuckCnIKk5 RMRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=EGGKNrPOLX/N2gQnpJHvJaZ4GLMl2zV2fBq/6LlBRpI=; b=LxFruZQMeYbM1W5u910P0EqlOa7ZGIBpcTyoazwtCGWoBCxdihuM28SYDc/5OMUegv ZzY9hK9LpqYJ3BVvLisyqbCo/rEDLzRkk0SUHL2fkNU+hcjNz8rV7MtL76OMFFo4Gvxf mJhaLND+hGQFB9oAK4LxYSLfucnFXZcrrLZU4Z5S/G5IYhNF3gE4DZ9vdALCHc4o9YeN cZJbdeEclLoa0RbCTIV8UpbrOwNEKnAA3/8x2kWLbLpO+gPB9lP4O3t4lsMf4l8eDUQT Bvj06WRDa4CcW2lYD509wMlTbfk91Sdfo2HPti8ZnudpMDZJI4MT0qtWSL7ng+Vq0/Gt mbVw== X-Gm-Message-State: AOAM533onLZQnL7r9DfYLcnDaf7/lO4DA4V83MEeNFHhGm+B0EWSGMAr wJs85Nq0fwBQSJ/okemdJsatGwbh/aOoug4an7Y= X-Google-Smtp-Source: ABdhPJwLNauCrq1hVAKy3kIo3n1mdr+pZSSHoCbSQFXHLcWmujjqSutxQ5TJE9NOQ/gFZRSxv6IL8DPPwBYgPc3YPiw= X-Received: by 2002:a05:651c:1303:: with SMTP id u3mr566574lja.95.1611593352471; Mon, 25 Jan 2021 08:49:12 -0800 (PST) MIME-Version: 1.0 References: <20210124211100.GI21030@mcvoy.com> <202101242114.10OLEYGk966708@darkstar.fourwinds.com> <20210124212525.GJ21030@mcvoy.com> <202101242333.10ONXjcI974038@darkstar.fourwinds.com> <202101250021.10P0L3Z2976588@darkstar.fourwinds.com> <6557f782-ecb1-6476-1eda-e23f30f9bbea@bitsavers.org> <20210125160430.GR21030@mcvoy.com> In-Reply-To: From: Richard Salz Date: Mon, 25 Jan 2021 11:49:01 -0500 Message-ID: To: Dan Cross Content-Type: multipart/alternative; boundary="0000000000004be89d05b9bc5192" Subject: Re: [TUHS] tangential unix question: whatever happened to NeWS? X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: TUHS main list Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --0000000000004be89d05b9bc5192 Content-Type: text/plain; charset="UTF-8" > It had no XDR because it was "reader makes it right" and datatypes > > were tagged. >> >> That's the first I've heard of that and I really like it. Most of the >> time, you are on a network of machines that are the same, so why have >> a network byte order, reader makes it right will just work. Neat. >> > > I guess I don't quite understand that. I can get how it works for simple > data types (integers, floating point numbers, perhaps strings) but it seems > like it breaks > It was only for native types https://pubs.opengroup.org/onlinepubs/9629399/chap14.htm The other things -- struct, array, pointers, etc -- have rules. See the link if you care for nitty-gritty details. --0000000000004be89d05b9bc5192 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> It had no XDR because it was "reader makes it ri= ght" and datatypes
> were tagged.

That's the first I've heard of that and I really like it.=C2=A0 Mos= t of the
time, you are on a network of machines that are the same, so why have
a network byte order, reader makes it right will just work.=C2=A0 Neat.
=

I guess I don't quite understand that.= I can get how it works for simple data types (integers, floating point num= bers, perhaps strings) but it seems like it breaks

It was only for native types=C2=A0 https://pubs.opengro= up.org/onlinepubs/9629399/chap14.htm=C2=A0=C2=A0 The other things -- st= ruct, array, pointers, etc -- have rules.=C2=A0 See the link if you care fo= r nitty-gritty details.

--0000000000004be89d05b9bc5192--