zsh-users
 help / color / mirror / code / Atom feed
From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: The elements of enlightenment
Date: Mon, 5 Dec 2022 20:58:54 +0100	[thread overview]
Message-ID: <CAN=4vMqKXudgwwQAPNzJ0OymhYWwPWu+ec+LyiVK2nhDP1jbeg@mail.gmail.com> (raw)
In-Reply-To: <819c9630-f315-8b1c-cb52-3d3ae8de2d5c@eastlink.ca>

On Mon, Dec 5, 2022 at 8:36 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> But, since setopt is a builtin anyway, why not just use it as is?

Parsing things from text is usually more complex than dealing with the
things that are already in a decent data structure. Your specific task
may be an exception if you really want to produce the same output as
`setopt` but with "off" in red. In this case it may be even desirable
to manipulate the output of `setopt` rather than reconstructing it
manually.

> printf is heavy, no?  setopt might be lighter?

Neither printf nor setopt are heavy. Forks are extremely inefficient
though. The cost of a fork is almost astronomical compared to simple
operations. The following two lines achieve the same thing:

    var=$(printf hello)
    printf -v var hello

On my machine the first line is 1500 times slower than the second. You
need to execute this line only 100 times in order to have the total
run time of a script in excess of 1 second. Imagine if every line of a
script was this slow.

Roman.


  parent reply	other threads:[~2022-12-05 20:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-05 15:57 Ray Andrews
2022-12-05 16:24 ` Roman Perepelitsa
2022-12-05 18:30   ` Bart Schaefer
2022-12-05 19:35   ` Ray Andrews
2022-12-05 19:44     ` Bart Schaefer
2022-12-05 19:58     ` Roman Perepelitsa [this message]
2022-12-05 21:20       ` Ray Andrews
2022-12-05 21:49         ` Roman Perepelitsa
2022-12-05 23:52           ` Ray Andrews
2022-12-06  0:17             ` Bart Schaefer
2022-12-06  1:34               ` Ray Andrews
2022-12-06 18:55             ` Roman Perepelitsa
2022-12-06 19:45               ` Bart Schaefer
2022-12-06 20:01                 ` Roman Perepelitsa
2022-12-06 20:07                   ` Bart Schaefer
2022-12-06 20:22                     ` Roman Perepelitsa
2022-12-06 23:52               ` Lawrence Velázquez
2022-12-07  1:04                 ` Lawrence Velázquez
2022-12-05 21:49         ` Bart Schaefer
2022-12-05 21:51           ` Bart Schaefer
2022-12-05 22:24           ` Ray Andrews
2022-12-05 23:24             ` Bart Schaefer
2022-12-06  1:47               ` Ray Andrews
2022-12-06  6:39 ` Lawrence Velázquez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAN=4vMqKXudgwwQAPNzJ0OymhYWwPWu+ec+LyiVK2nhDP1jbeg@mail.gmail.com' \
    --to=roman.perepelitsa@gmail.com \
    --cc=rayandrews@eastlink.ca \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).