finkel@TAURUS.BITNET (04/12/88)
I was looking at my RKM a few days ago when I decided to expand my knowledge about the clist.library . It's documented only in the appendix, with information on each routine. there is no general explanation about the library as a whole. Anyway, from what I understood, clist.library can handle variable length strings, and my assumption is that these are not null terminated ones, but the can contain nulls like basic strings. Am I right? Another problem is that I have found an InitCPool routine to create a pool from which to allocate strings, but there is no routine like FreeCPool. How do you free a CPool? Free it's memory, and then free any structures it's using? I am not near the books or the computer now, and I didn't check the the structures of clist.library . Also, names like Get Unget Put and UnPut are simply #%$#%. what's bad with PutFirst PutLast GetFirst GetLast or something smiliar? ------------------------------------------------------------------------------- Udi Finkelstein | Bitnet: finkel@taurus.bitnet or finkel@math.tau.ac.il Tel Aviv University | Internet: finkel%taurus.bitnet@cunyvm.cuny.edu Israel | UUCP: ...!psuvax1!taurus.bitnet!finkel -------------------------------------------------------------------------------
cmcmanis%pepper@Sun.COM (Chuck McManis) (04/13/88)
In another article (Udi Finkelstein) writes: > I was looking at my RKM a few days ago when I decided to expand my knowledge > about the clist.library. Don't bother. The clist stuff was pulled out in 1.2 because *no one* uses it and it they needed the ROM space. Heck it took over a year for anyone to notice it was missing! The standard C library code has quite reasonable set of string calls in it. --Chuck McManis uucp: {anywhere}!sun!cmcmanis BIX: cmcmanis ARPAnet: cmcmanis@sun.com These opinions are my own and no one elses, but you knew that didn't you.
ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab) (04/14/88)
In article <49212@sun.uucp> cmcmanis@sun.UUCP (Chuck McManis) writes: >In another article (Udi Finkelstein) writes: >> I was looking at my RKM a few days ago when I decided to expand my knowledge >> about the clist.library. > >Don't bother. The clist stuff was pulled out in 1.2 because *no one* uses >it and it they needed the ROM space. [ ... ] Then why didn't they relegate it to the WorkBench disk, rather than toss it completely? I imagine that it has *some* sort of use; otherwise they wouldn't have put it in the system in the first place. _-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ Leo L. Schwab -- The Guy in The Cape ihnp4!pacbell -\ \_ -_ Recumbent Bikes: dual ---> !{well,unicom}!ewhac O----^o The Only Way To Fly. hplabs / (pronounced "AE-wack") "Work FOR? I don't work FOR anybody! I'm just having fun." -- The Doctor
page@swan.ulowell.edu (Bob Page) (04/14/88)
I guess you haven't tried to OpenLibrary() the clist.library yet... Since the docs were incomplete, nobody really knew how to use it. Since nobody really knew how to use it, nobody used it. Since nobody used it, it was taken out of kickstart. If you want clist.library, you'll have to use KS1.1, as it was removed from 1.2. ..Bob -- Bob Page, U of Lowell CS Dept. page@swan.ulowell.edu ulowell!page
cmcmanis@sun.uucp (Chuck McManis) (04/15/88)
Chuck McManis (yours truly) wrote : >>Don't bother. The clist stuff was pulled out in 1.2 because *no one* uses >>it and it they needed the ROM space. [ ... ] In article <5689@well.UUCP> ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab) writes: > Then why didn't they relegate it to the WorkBench disk, rather than >toss it completely? I imagine that it has *some* sort of use; otherwise >they wouldn't have put it in the system in the first place. According to the 'lore' (the generic name for those Amiga stories one hears at the Oasis after the {ex}Amiga employees have comfortably consumed a few beers) the clist.library was created for *one* purpose, a version of BASIC that was never released. When 1.2 was in process they needed the ROM space. Again, there is no known use for the clist.library. -- --Chuck McManis uucp: {anywhere}!sun!cmcmanis BIX: cmcmanis ARPAnet: cmcmanis@sun.com These opinions are my own and no one elses. But you knew that, didn't you.
rap@ardent.UUCP (Rob Peck) (04/16/88)
In article <5689@well.UUCP>, ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab) writes: > In article <49212@sun.uucp> cmcmanis@sun.UUCP (Chuck McManis) writes: > >Don't bother. The clist stuff was pulled out in 1.2 because *no one* uses > >it and it they needed the ROM space. [ ... ] > > Then why didn't they relegate it to the WorkBench disk, rather than > toss it completely? I imagine that it has *some* sort of use; otherwise > they wouldn't have put it in the system in the first place. Yes, it DID have a use. When CAOS was being designed, the same company that was to implement CAOS was working on a BASIC interpreter that would complement(compliment,,,, naaahh) CAOS. This company insisted that unless they had a clist.library to refer to, it would be difficult (nay -- impossible) to meet their obligations on the BASIC within the time span of the original contract. Thus a lot of effort went into making the clist.library do what was requested. Not MY effort, but it was a was a "bear" of a job to accomplish within the requested time frame :^) and stayed with the system even though CAOS was not to be. You'll also note that with the replacement, AmigaDOS, Amy got ABasiC. So the clist.library became less important. Re the "missing docs" in the RKM - after looking over the man pages in the first place, it had seemed that the contents were pretty self-explanatory (my impression at the time anyhow) so we tech-responsibles spent more time documenting things for the RKM that did not stand alone so easily. Now that I look back at it, that was a reasonable decision. Rob Peck (writer/organizer of RKM's) ...ihnp4!hplabs!ardent!rap