Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!iuvax!bsu-cs!dhesi From: dhesi@bsu-cs.UUCP (Rahul Dhesi) Newsgroups: comp.sys.amiga.tech Subject: Re: zoo Message-ID: <4346@bsu-cs.UUCP> Date: 16 Oct 88 00:08:28 GMT References: <8810121728.AA14821@cory.Berkeley.EDU> <4305@bsu-cs.UUCP> <135@fishpond.UUCP> Reply-To: dhesi@bsu-cs.UUCP (Rahul Dhesi) Organization: CS Dept, Ball St U, Muncie, Indiana Lines: 20 In article <135@fishpond.UUCP> fnf@fishpond.UUCP (Fred Fish) writes: >If the zoo format definition doesn't have any "reserved for future use" >fields, then I guess you are out of luck... Actually it does, and what's more, they are defined in such a way that zoo archives containing these additional fields will remain downward compatible in the future. However, zoo archives have been steadily growing in size since 1986. Each new field that is added enlarges the archive slightly. This makes a difference especially if you have an archive containing many small files. The main reason for avoiding defining too many additional fields is the complexity of the archive (bigger archives) and the complexity of the code (bigger executable zoo), less space left on your disk. The MS-DOS zoo version 1.0 was 29 kilobytes; version 2.01 is now up to 40 K and still growing. -- Rahul Dhesi UUCP: !{iuvax,pur-ee}!bsu-cs!dhesi