Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!elroy.jpl.nasa.gov!swrinde!emory!gatech!prism!jgb
From: jgb@prism.gatech.EDU (James G. Baker)
Newsgroups: comp.databases
Subject: Re: Clipper: Okay, now I'm really pissed
Keywords: arrays SAVE
Message-ID: <27535@hydra.gatech.EDU>
Date: 28 Apr 91 03:02:59 GMT
References: <1991Apr27.210921.9751@anomaly.sbs.com>
Organization: Georgia Institute of Technology
Lines: 30

In article <1991Apr27.210921.9751@anomaly.sbs.com> mpd@anomaly.sbs.com (Michael P. Deignan) writes:
>BUT YOU STILL CAN "SAVE TO" THE F**KING THINGS!
>
>What good is an array if you can't SAVE it in a MEM file and recall it at
>a later time? What good is setting up that array of user-customized default
>program operation flags if you can't SAVE them?

Sorry you're so upset.  Although there *are* libraries out there for a
few cents that will allow you to save arrays, you could write a function
that would save an array's contents to a disk file or database.  It's a 
bit of a kludge, but back with '86 (when arrays were a dream) and even '87
I concatenated all the elements with ~ separating them.  Multi-dimensional
arrays would be trickier - probably worth the library.

It is more complicated to save arrays than ol' memvars.  The dimensions 
are fairly dynamic and each element can be different data types, which is
nice but undoubtedly hell for the compiler to do right.

If its just 1-dim array, maybe the {item1}~{item2}~ will work for you.
Good luck.





-- 
BAKER,JAMES G - Undergraduate Lab Instructor, School of Electrical Engineering
____  _    _    Georgia Institute of Technology, Atlanta Georgia, 30332
  |  | _  |_)   uucp: ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!jgb 
(_|. |_). |_).  Internet: jgb@prism.gatech.edu, jgb@ee, jgb@eecom, jgb@cc