Re^2: parse lisp style config

Replies are listed 'Best First'.
Re^3: parse lisp style config by vincentaxhe (Scribe) on Nov 28, 2024 at 01:08 UTC
I found those standard tools have their peculiarities and complains always, I just want to express an struture, and not too hard to parse, I heard lisp's way is easy to parse and extendable, I'm trying and practising, though using only brancket may be not a good idea which leads to express array in a funny way, I will find out, now I'm using toml as easy reading config format.	[reply]
Re^4: parse lisp style config by GrandFather (Saint) on Nov 28, 2024 at 06:31 UTC
To my mind "easy to parse" is not having to write any parsing code at all. That is, use someone else's effort and focus your effort on added value. Anything else is either doing it to learn (laudable), or NIH (not invented here) syndrome (fundamentally bad). Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond	[reply]
Re^4: parse lisp style config by Danny (Chaplain) on Nov 28, 2024 at 17:14 UTC
Why not just make your config a perl data structure?	[reply]
Re^5: parse lisp style config by afoken (Chancellor) on Nov 28, 2024 at 22:49 UTC
Why not just make your config a perl data structure? Because parsing Perl in a safe way is hard. You don't want to execute the "rm -rf /" in $config={ foo => `rm -rf /` }. See also: Re^4: how to read conf file in perl script Re: What's the right way to include a config file as a .pm bareword? Re^2: Storing state of execution Re^4: The safety of string eval and block eval. Re: Accessing variables in an external hash without eval Re^2: conf file in Perl syntax Alexander -- Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)	[reply] [d/l]
Re^6: parse lisp style config by cavac (Prior) on Dec 05, 2024 at 13:26 UTC