Re:Better bash in 15 minutes
by mateuszf on Wednesday April 16, 2014 @02:19AM
(#7596375)
Nice here document feature I have found recently is heredoc with pipe, e.g.
It allows to pass heredoc text to standard input of next command.
[ Parent
| on HN ]
This is a prime example of useless use of cat. Heredoc already means "pass this as stdin", there's no need to pipe it. Your example without cat:
curl http://localhost -d @- <<REQUEST_BODY
{
"from" : 0,
"size" : 40
}
REQUEST_BODYI like modularity:
request_body() {
cat <<REQUEST_BODY |
{
"from" : 0,
"size" : 40
}
REQUEST_BODY
}
get_url() {
curl http://localhost -d @-
}
request_body | get_url
I find it helps readability when you come back to it a year later. Of course, it's also easy to parameterize the body, if needed./readability sometimes trumps YAGNI
Well, maybe in that case it is.
But I like to separate the commands so that the data flow looks sequential. That way it makes more sense to me.
Re:Better bash in 15 minutes
by zimpenfish on Wednesday April 16, 2014 @05:59AM
(#7596878)
Much as I hate the cargocult invocation of "UUOC", this is actually nicer because it reads more sanely - the HEREDOC is properly linked to the curl whereas the previous has the curl seemingly adrift on its own line unattached to the HEREDOC.
Re:Better bash in 15 minutes
by zimpenfish on Wednesday April 16, 2014 @06:02AM
(#7596885)
My issue with this is that unless you're maintaining a lot of context and understanding the precise weirdness of HEREDOC piping, that looks at first glance like you're catting the HEREDOC to STDOUT and then running a random curl command. It's clever, sure, but it's harder to read and maintain.