I might be misunderstanding you, but I don't think you are talking about persistence. You wouldn't want your entire CD music library in a persistent object.
All you need is the CD music library as a regular database, and then if you need a persitent object pointing to a prticular CD, you make that 1 CD object persitent - not the whole library.
I.e., when your program ends, you would serialize the object using Data::Dumper or Storable or other. Then, when your program next starts, you decode the serialized object (if it exists) and use that object again. The looping you talk about is quite seperate from the persistence.
$ perldoc perldoc
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.