home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.pascal
- Path: sparky!uunet!spool.mu.edu!umn.edu!csus.edu!borland.com!chard
- From: chard@borland.com (Richard Nelson)
- Subject: Re: Distributing TPUs
- Message-ID: <1992Dec31.223422.18687@borland.com>
- Originator: chard@genghis.borland.com
- Sender: news@borland.com (News Admin)
- Organization: Borland International
- References: <dmurdoch.253.725377977@mast.queensu.ca> <1992Dec27.022633.14853@beaver.cs.washington.edu>
- Date: Thu, 31 Dec 1992 22:34:22 GMT
- Lines: 22
-
- In article <1992Dec27.022633.14853@beaver.cs.washington.edu> andrewb@lynx.cs.washington.edu (Andrew Berg) writes:
- >
- >Does anyone know what the motivation for not ever having any backward com-
- >patibility between any of the TPU formats? It seems like it would be a useful
- >thing.
-
- It's not really a question of motivation, it's a matter of what a
- compiled unit IS. The TPU (or TPP or TPW, depending on your target
- platform) is essentially a processed image of the compiled code and
- its symbols and such. It's in the format that the compiler and linker
- want to use it, which is why it's so fast. But that also means that
- when the compiler changes in any significant way (which is one of the
- reasons for a new version, eh?), the information in the compiled unit
- also changes.
-
- That's the simplified description, anyway.... It's not just Borland
- being perverse. :-)
- --
- =========================================================================
- Richard Nelson, Borland Int'l | chard@borland.com | Go Bears! Grrr-rah!
- Had this been Borland's opinion, I would have written it in a manual.
- "I met a girl who sang the blues, and I asked her for some happy news."
-