From owner-freebsd-current  Sun May 31 18:22:14 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA01911
          for freebsd-current-outgoing; Sun, 31 May 1998 18:22:14 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from aldan.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA01904
          for <current@freebsd.org>; Sun, 31 May 1998 18:22:08 -0700 (PDT)
          (envelope-from mi@rtfm.ziplink.net)
Received: from rtfm.ziplink.net (rtfm [199.232.255.52])
	by aldan.ziplink.net (8.8.8/8.8.7) with ESMTP id BAA25305
	for <current@freebsd.org>; Mon, 1 Jun 1998 01:21:59 GMT
	(envelope-from mi@rtfm.ziplink.net)
Received: (from mi@localhost)
	by rtfm.ziplink.net (8.8.8/8.8.5) id VAA25839
	for current@freebsd.org; Sun, 31 May 1998 21:22:03 -0400 (EDT)
From: Mikhail Teterin <mi@aldan.algebra.com>
Message-Id: <199806010122.VAA25839@rtfm.ziplink.net>
Subject: TenDRA/XANDF to the rescue? (Re: Fix for undefined...)
In-Reply-To: <199805312213.PAA16988@usr06.primenet.com> from "Terry Lambert" at "May 31, 98 10:13:11 pm"
To: current@FreeBSD.ORG
Date: Sun, 31 May 1998 21:22:02 -0400 (EDT)
X-Face: 
	%UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
		 hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
		 y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Terry Lambert once stated:

=I agree that at some point you are going to lose backward compatability;
=I think, however, that XANDF will push this off, since most of the
=historical compatability issues can be resolved by regenerating the
=assembly code, and relinking, which is implied.

Well, what's wrong with plain C-code, for example? Just because it
is source and is easier to reverse engineer? Theoreticly, C must
be as crossplatform as XANDF or whatnot. Ok, how about Java byte
code?

=I *really* look forward to the day when I can buy an XANDF Motif
=library, and use it on all my hardware, regardless of the CPU type.
=8-0.

How about buying Java byte code Motif library and compiling it into
native binary for all your hardware regardless of the CPU type? Or
is XANDF better suited as an intermidiate between source and native?
Is it so much better suited that it is worth it to have yet another
format?

	-mi

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message