ChanServ changed the topic of #picolisp to: PicoLisp language | Channel Log: https://irclog.whitequark.org/picolisp/ | Check also http://www.picolisp.com for more information
orivej has joined #picolisp
wineroots has quit [Remote host closed the connection]
orivej has quit [Ping timeout: 276 seconds]
aw- has quit [Quit: Leaving.]
aw- has joined #picolisp
_whitelogger has joined #picolisp
orivej has joined #picolisp
wineroots has joined #picolisp
aw- has quit [Ping timeout: 264 seconds]
aw- has joined #picolisp
aw- has quit [Quit: Leaving.]
<beneroth> Regenaxer, just fyi, I see the ml discussion as same as you (re Tomas)
<Regenaxer> Good, thanks! :)
<Regenaxer> I don't understand what his problem is
<beneroth> focused solutions (as you're are) are focused, ofc they are not optimal for cases they were not meant for
<Regenaxer> T
<beneroth> I guess he understands your examples "that is the way to do HTML/PDF in picolisp" but then that was not the topic
<Regenaxer> yes, he is in fact a good Pil programmer
<Regenaxer> (or was some years ago)
<beneroth> T
<beneroth> your strategy to programming is (as I understand it): solve the requirements. no extra bells and whistles, KISS and tiny and clean.
<beneroth> generally people just prefer "give me library/example to do X" without having to think too hard / specify too detailed what X entails
<beneroth> which of course is also a way.. but that is the way which leads to bloat, mistakes and especially security mistakes
<Regenaxer> exactly
<Regenaxer> I'm walking in the rain, but could not resist now writing another short mail to the list ;)
<beneroth> :)
<beneroth> I consider FEXPR to be handy for DSL's
<beneroth> especially for the exact things Tomas went on about... printing vs. building a data structure. the DSL code can be the same for both scenarios, just throw them into different FEXPR which use different function bindings when evaluating the DSL prog
<beneroth> e.g. I use input parsing FEXPR's which re-bind (line) or (eol) and customize them to whatever makes sense for the input (e.g. XML which have quite different record line/structure than a CSV)
<beneroth> so I get a small DSL to handle the input of the file, and it looks same as standard picolisp reading text files with (in File ... (line) (skip) ..) but I in my use case I use a FEXPR in place of (in)
* beneroth suspects he should write this to the ML...
<beneroth> FEXPR's are interpreters, it's simply that
<Regenaxer> ret
<Regenaxer> Terrible
<Regenaxer> Rain and storm, I'm completely wet
<Regenaxer> yes, DSL's
<Regenaxer> haha, yes :) To ML would be ideal
<beneroth> we have it windy, but no rain yet
<Regenaxer> I see, but very windy I presume. Stormy here
<beneroth> yeah very windy
orivej has quit [Ping timeout: 245 seconds]
orivej has joined #picolisp
orivej has quit [Ping timeout: 246 seconds]
theruran has quit [Quit: Connection closed for inactivity]
theruran has joined #picolisp