octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #60413] build: sed expression problems when pr


From: Rik
Subject: [Octave-bug-tracker] [bug #60413] build: sed expression problems when prefix is empty or slash
Date: Wed, 28 Apr 2021 17:27:19 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.72 Safari/537.36

Follow-up Comment #24, bug #60413 (project octave):

I meant to state the ${} syntax.  The space will delimit the name so there is
no ambiguity in interpretation as Mike mentioned.

Question is whether we also want consistency.  For example,


mk-version-h.in.sh:  -e "s|%OCTAVE_VERSION%|\"${OCTAVE_VERSION}\"|"


We could write just "$OCTAVE_VERSION" here, right?  It's fine with me any of
the three ways: 1) $SED, $OCTAVE_VERSION, 2) ${SED}, ${OCTAVE_VERSION}, or 3)
$SED, ${OCTAVE_VERSION}.

And to answer jwe's question, one needs to use quotes if the variable expands
to include a space.  So, "$SED" or "${SED}".


  It's fine with me either way.  The space will delimit the name.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60413>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]