in reply to parse lisp style config

Are you doing this as a learning exercise, or have you an intended use in mind where this is just a tool? If the latter, why not use one of the "standard" tools such as YAML, JSON, ini, ...?

Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond

Replies are listed 'Best First'.
Re^2: parse lisp style config
by afoken (Chancellor) on Nov 27, 2024 at 23:42 UTC
    why not use one of the "standard" tools

    https://xkcd.com/927/

    Alexander

    --
    Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
[reply]
      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]

        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]
        Why not just make your config a perl data structure?
[reply]

In Section Seekers of Perl Wisdom