bug-wget
[Top][All Lists]
Advanced

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

[Bug-wget] [bug #54826] too much output on wget --version


From: Tim Ruehsen
Subject: [Bug-wget] [bug #54826] too much output on wget --version
Date: Fri, 12 Oct 2018 10:31:14 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0

Follow-up Comment #5, bug #54826 (project wget):

The best reason to *keep* that ouput is that is was put like that ~10years (or
maybe 20 ?) ago. There are production scripts out there that parse the output
of wget --version.

Apart from that, you are right. And I wish we could just drop bw compat. At
least that would be more fun - but we have to be responsible as well.

And LLVM is just a completely different approach to compilation / translation.
LowLevelVirtualMachine... gcc could translate into it as well... but the
ethics are different and thus the licenses.

And comparing clang / gcc as frontend to the C language... clang still refuses
to compile nested functions which is a blocker to use it in my company. We use
nested functions since 20 years, no way to rewrite the stable code (makes it
much more complicated and would introduce bugs).

And gcc can so so much more, see
https://www.linux.com/blog/2018/10/gcc-optimizing-linux-internet-and-everything

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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