Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!apple!rutgers!ucsd!ucsdhub!jack!crash!pnet01!haitex
From: haitex@pnet01.cts.com (Wade Bickel)
Newsgroups: comp.sys.amiga.tech
Subject: Re: How satisfied are you with IFF?
Message-ID: <3446@crash.cts.com>
Date: 18 Sep 88 16:53:36 GMT
Sender: news@crash.cts.com
Organization: People-Net [pnet01], El Cajon CA
Lines: 33

rap@ardent.UUCP (Rob Peck) writes:

        [discussion of JIFF, deleted.  Subject is my suggestion to re-do
           IFF.]

>Posted in the hopes of preventing reinventing the wheel and letting
>Wade get on to the more important things in life, like creating real
>(money-making?) software for Amy.
>


        So far I have only spec'd the thing.  The purpose is to allow more
flexability in the reading of complex data.  The nice thing about the method
I've come up with is that it is very simple and straitforward.  The actual
writer code (not including the low level io stuff, such as WriteBytes) is
only about 10 lines of code.  The support routines (used to locate the data
to be written and specify what kind of chunks it should be stored in) take
up perhaps another 100 lines, max.    The reader is a bit more complicated,
but would make things like ANIMS, or ANIMS where multiple paths (for Laser
Disk like applications) reasonable undertakings.

        As far as getting on with creating "real" software, that's what I AM
doing.  Otherwise I'd spend a month writing this code, and just present it.


                                                      Thanks,

                                                                Wade.

UUCP: {cbosgd, hplabs!hp-sdd, sdcsvax, nosc}!crash!pnet01!haitex
ARPA: crash!pnet01!haitex@nosc.mil
INET: haitex@pnet01.CTS.COM
Opionions expressed are mine, and not necessarily those of my employer.