Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!clyde.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!julius.cs.uiuc.edu!apple!uokmax!servalan!epmooch!ben From: ben@epmooch.UUCP (Rev. Ben A. Mesander) Newsgroups: comp.sys.amiga.programmer Subject: Re: C string library? Message-ID: Date: 8 Feb 91 00:21:44 GMT References: <874@cbmger.UUCP> Lines: 34 >In article <874@cbmger.UUCP> peterk@cbmger.UUCP (Peter Kittel GERMANY) writes: >Now it should be possible to have a set of functions which initialize >a memory area and allocate dynamically all my strings in that space >just as a Basic interpreter does. Plus a good and fast garbage collection. >And plus all the nice string functions that make Basic programming such >a fun. And if you would add further flexibility over the Basic approach, >then one could add dynamic growth of the whole string area, where you >in Basic once and for all must decide for a certain amount by CLEAR. > >So, is there such a beast out there? > Try creative use of the C libraries realloc() function call. >BTW: Converting Basic to C by hand isn't that difficult! Just take any >editor, do some global search and replace (":" --> ";", "IF " --> "if(", >"END IF" --> "}", and so on), and do some recoding on things like >OPEN or WINDOW, and you already have most of the work done. Worse is >it with such simple things like INPUT or INKEY$ :-(. Yes, AND strings. Sounds like you might be able to write a sed, awk, perl, or MicroEMACS program to do most of the grunt work. >-- >Best regards, Dr. Peter Kittel // E-Mail to \\ Only my personal opinions... >Commodore Frankfurt, Germany \X/ {uunet|pyramid|rutgers}!cbmvax!cbmger!peterk -- ben@epmooch.UUCP ben%servalan.UUCP@uokmax.ecn.uoknor.edu {chinet,uokmax}!servalan!epmooch!ben (Ben Mesander) War in gulf: newpath 288 396 216 0 360 arc 288 612 moveto 288 180 lineto 288 396 moveto 136 244 lineto 288 396 moveto 440 244 lineto 36 setlinewidth stroke showpage