svn commit: r326554 - in head: . usr.bin/sponge usr.bin/sponge/tests usr.bin/tee

[Devin Teske]

> On Dec 5, 2017, at 5:00 AM, Hans Petter Selasky <hps at selasky.org> wrote:
> 
>> On 12/05/17 13:58, Rodney W. Grimes wrote:
>> Further more, why does freebsd need this in base?
> 
> Hi,
> 
> I think this is useful. It could replace the "-i " (intermediate) option for "sed" for example. It avoids creating temporary files when filtering files, right?
> 
> --HPS
> 

Wth is wrong with:

data=$( sed -e '...' somefile ) &&
        echo "$data" > somefile

or

set -e
data=...
echo "$data" > ...

or

exec 3<<EOF
$( ... )
EOF
cat > ... <&3

or

(I digress)

Infinite variations, but the gist is that sponge looks to be trying to help sh(1)/similar when help is unneeded.

Why buffer data into memory via fork-exec-pipe to sponge when you can buffer to native namespace without pipe to sponge?

Am I missing something? Why do we need sponge(1)?
-- 
Devin