Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!ames!ncar!tank!eecae!cps3xx!usenet
From: usenet@cps3xx.UUCP (Usenet file owner)
Newsgroups: comp.sys.amiga
Subject: IFF.library (was: Re: Stupid Wishes)
Message-ID: <3373@cps3xx.UUCP>
Date: 12 Jun 89 19:26:04 GMT
References: <17161@swrinde.nde.swri.edu> <108759@sun.Eng.Sun.COM> <17222@swrinde.nde.swri.edu> <19361@cup.portal.com>
Reply-To: porkka@frith.UUCP (Joe Porkka)
Followup-To: comp.sys.amiga
Distribution: usa
Organization: Michigan State University
Lines: 17

In article <19361@cup.portal.com> stephan@cup.portal.com (Stephen Derek Schaem) writes:
>
> Well the idea could be; From CBM to make a disk based iff library that

I don't remember who, but I seem to recall
that somebody said they were working on an iff.library.

Question to whom ever you are: How are you going to deal with the
multitude of different forms?

I simple idea that I had is: have libraries of the name IFFform.library,
where 'form' is the 4letter form code. There would also be a
IFFgeneral.library that each of the IFFform.libraries would open and
use. This would make it easy for anybody to extend their iff libraries.


This is an example of a short .signature   jap@frith.cl.msu.edu