[CrackMonkey] [mailman-owner@zork.net: CrackMonkey Subscribe Notification]

[Aaron Lehmann]

On Mon, Jul 31, 2000 at 07:59:18PM -0700, Monkey Master wrote:
> begin  Aaron Lehmann quotation:
> > Exactly my point. Berkeley DB makes it easy to seek() and load data
> > when you need it. Not loading a text configuration file into core
> > while running would probably cause parsing nightmares, as well as a
> > loss of speed due to parsing.
> 
> 	But the whole point of reading in a configuration file is to
> populate configuration data structures.  YOu're not REALLY keeping
> that .foorc file around in RAM-- it just sets environment variables
> and so forth.  

Umm, you're keeping its data in RAM. But my whole point is moot ever
since I realized that EFM uses a DB for each directory. So don't
listen to me.

> 	The task of reading in configuration data does not map onto
> editing of arbitrary-length files.
> 
> -- 
> CrackMonkey.Org - Non-sequitur arguments and ad-hominem personal attacks
> LinuxCabal.Org  - Co-location facilities and meeting space 
> Pigdog.Org      - The Online Handbook for Bad People of the Future
>                 You are not entitled to your opinions.
> 
> 
> _______________________________________________
> CrackMonkey: Non-sequitur arguments and ad-hominem personal attacks
> http://crackmonkey.org/mailman/listinfo/crackmonkey