On 5/21/18 Chet Ramey wrote:
> What you're asking for is syntactic sugar for:
> some-command > temp-file
> echo '#' >> temp-file
> variablename=$(< temp-file)
> rm -f temp-file
> variablename=${variablename%?}
> I would look at a sample implementation, possibly using mmap, if someone
did one.
On 6 December 2016 at 00:19, Greg Wooledge wrote:
> what evidence?
> [for shell scripting builds]
>
I suppose the evidence that you want is in the very same wikipedia article
about make, where it says precisely that shell scripts were used before
make came along.
However, please remember I a
You have gone to some trouble with your answer Eduardo, and thanks for that
but really you are arguing against a proposition that I have not put and I
do not want other readers to be mislead. I am asking about shell scripting
of software builds, something that is perfectly possible to do and once
m
On Fri, Dec 02, 2016 Greg Wooledge wrote:
"For starters, make is *older* than bash, by over a decade.
"https://en.wikipedia.org/wiki/Make_%28software%29 says that make
originated at Bell Labs in April 1976.
"https://en.wikipedia.org/wiki/Bash_%28Unix_shell%29 says that the first
"beta version of ba
On 29/11/16 Charles Daffern replied to my question about bash and make as
if I was proposing that bash might beneficially reimplement make, but
really I am asking why should not program builds have been scripted with
bash all along and make never invented. So if Charles or someone else could
point
than some file that is required.
On 29 November 2016 at 02:21, Dennis Williamson wrote:
>
>
> On Sun, Nov 27, 2016 at 7:25 PM, Robert Durkacz
> wrote:
>
>> Has thought been given, over the years, to extending bash to do
>> what make does, in the obvious way that I am
make has survived all this time but it is not very well accepted today with
a lot of competing build systems trying to do better. bash is very secure
and moreover the Bourne shell was there first. make is falling out of
favour as far as I can see even though it has had a very good run:
Kernighan an
Has thought been given, over the years, to extending bash to do
what make does, in the obvious way that I am about to describe?
It would be a matter of having chosen build commands do nothing if their
outputs are newer than their inputs. For example that is, cc file.c -o
file.o should execute norm
This is a request for a new feature. Perhaps there are good reasons
why it can't be done, but from the outside looking in it seems
possible, and I have taken into account advice from the bash help
mailing list.
Could there be a dry-run option for bash. A dry-run option would be
something akin to a
