Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: rbowman Newsgroups: comp.os.linux.misc Subject: Re: Warning - Serious 'sudo' Flaw Compromises Security Date: 16 Oct 2025 06:57:18 GMT Lines: 25 Message-ID: References: <10cdluk$pc59$2@dont-email.me> <1NucnW53DZrMOHH1nZ2dnZfqnPGdnZ2d@giganews.com> <10cihiq$23kb8$6@dont-email.me> <10cios3$25sim$2@dont-email.me> <10cj667$29n96$5@dont-email.me> <10cjf5m$2cnh5$2@dont-email.me> <20251013114536.00000ae5@gmail.com> <10cmkub$39hde$3@dont-email.me> <20251015083926.0000473b@gmail.com> <10cpdjj$1ru9$3@dont-email.me> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net 276tNYaoc8G0b18uG6+30AaGYZGhrFYZ6NlbYdfMo18X5B3PKd Cancel-Lock: sha1:uS7LStlcEmZxsSI9MCDJFnGCKRY= sha256:c2VwWDc8ri80e1tCulFWJ86VC54E3+81wj4pv/7YWuU= User-Agent: Pan/0.162 (Pokrosvk) Xref: csiph.com comp.os.linux.misc:76236 On Thu, 16 Oct 2025 00:17:55 -0000 (UTC), Lawrence D’Oliveiro wrote: > On Wed, 15 Oct 2025 08:39:26 -0700, John Ames wrote: > >> ... for classroom purposes it'd probably be best to find something with >> both *A.* practical application in a real-world context ... and *B.* a >> real case to be made for a recursive solution beyond simple novelty >> value. > > How about parsing JSON and XML, then? They are so heavily used in > real-world software development these days, it becomes helpful to > understand how to deal with them. I always turned XML over to expat. https://libexpat.github.io/ Setting up the handlers for the different depths for the first time takes some trial and error but it's fast once you understand the patterns. For documents where I'm trying to produce human readable output I use XSLT. Writing a parser wouldn't be difficult but why reinvent the wheel and have to fix all the edge case bugs that were already handled. I could use expat because it was public domain. It finally was given a MIT license but no StallmanShit (tm).