From mboxrd@z Thu Jan 1 00:00:00 1970 Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.lang.ada Subject: Re: systemd controversy Date: Tue, 19 Mar 2024 22:29:50 -0000 (UTC) Organization: A noiseless patient Spider Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Tue, 19 Mar 2024 22:29:50 -0000 (UTC) Injection-Info: dont-email.me; posting-host="cf2257effda993e7401c0124f815988b"; logging-data="1136326"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1++w/5eYqPR/bIOv6Uf36Sp" User-Agent: Pan/0.155 (Kherson; fc5a80b8) Cancel-Lock: sha1:7PPoRZfR5Wqel4/ijWrnTcH4yKk= Xref: news.eternal-september.org comp.lang.ada:66145 List-Id: On Tue, 19 Mar 2024 10:16:50 -0000 (UTC), Kevin Chadwick wrote: >>The declarative systemd unit-file syntax should be easier to translate >>to other forms than perhaps going the other way. > > I can't see how non portable unit files backed by c code are more > helpful than atleast more portable scripts with less c per command to > interpret, to be honest. The unit files are in the classic .INI file format, which has been around for decades. Code for parsing it should be readily available for every language in common use. Scripts need an interpreter. Being Turing-complete, in general information cannot be extracted from them except by running them. Unit files have a fixed vocabulary of keyword entries, which can be easily enumerated, looked up, whatever. That’s what’s meant by “declarative”.