On Tue, Dec 25, 2018, at 10:11, Cág wrote:
> 3. Are there any drop-in replacements for Open/LibreSSL and GNU make?
I've thought about this for a while, and I wonder if make is even
needed? Or rather, what's wrong with:
cc [flags] *.c
If you have a reasonably fast compiler then using object f
On Thu, Dec 27, 2018, at 08:46, Hiltjo Posthuma wrote:
> // is not ANSI.
Is there a good reason for sticking with ANSI C? It's my understanding
that even most small/minimal compilers support C99 (or most of it)?
The coding style document even endorses it: "Use C99 without extensions
(ISO/IEC 9899
On Wed, Dec 26, 2018 at 10:44 AM wrote:
> Preprocessor. I guess having 2 ways to define comments is not significant,
> then better stick to one and the historical one.
Better than one way is zero ways -- comments are not semantically
significant, so rather than argue about which standards-defined
On Thu, Dec 27, 2018 at 12:56:29AM +1300, Martin Tournoij wrote:
> The coding style says:
>
> > Use /* */ for comments, not //
>
> Don't want to start a discussion about it, but I'm curious why // is
> disallowed? AFAIK all compilers accept // these days, and have for a
> long time?
>
> I've alw
Dear Quentin,
Any ideas what can be done in order to make Surf reading local files?
Regards,
Piotr
On Mon, 24 Dec 2018 22:49:28 +0100
Piotr wrote:
> On Mon, 24 Dec 2018 22:35:31 +0100
> Quentin Rameau wrote:
>
> > Hi Piotr,
> >
> > > I installed latest stretch-backports version of surf, b
On Wed, Dec 26, 2018 at 09:39:29AM -0600, Cág wrote:
> Would systemd be bug-free, it would still suck. It's not only the language
> or bugs. PulseAudio is C, too ^_^
I send you back to one of my previous email why saying this is an intellectual
falacy. Let's reverse this falacy: jack is pure cr*p
On Thu, Dec 27, 2018 at 12:56:29AM +1300, Martin Tournoij wrote:
> ... AFAIK all compilers accept // these days ...
Preprocessor. I guess having 2 ways to define comments is not significant,
then better stick to one and the historical one.
--
Sylvain
Martin Tournoij wrote:
The chosen language is just one "suckless metric". I hold little love
for C++, but I'll choose a well-designed and well-written C++ program
over a badly designed and badly written C program any day of the week.
A good example to illustrate this point might be procmail:
ht
On Thu, Dec 27, 2018 at 12:51:08AM +1300, Martin Tournoij wrote:
> On Wed, Dec 26, 2018, at 13:23, Sylvain Bertrand wrote:
> > Since llvm is pure c++ madness and gcc is still far from being one:
> > gnu gcc sucks less than clang/llvm. yes, GNU gcc sucks less than BSD
> > clang/llvm, wow.
>
> The c
Martin Tournoij wrote:
1. Is there any network utility suite like net-tools or iproute2 but
sane and active? Or maybe net-tools was forked by somebody?
Usually the stuff you want to do with these tools are limited to just a
few tasks ("connect to wired network", "connect to wireless network",
The coding style says:
> Use /* */ for comments, not //
Don't want to start a discussion about it, but I'm curious why // is
disallowed? AFAIK all compilers accept // these days, and have for a
long time?
I've always preferred // since they can nest (you can comment out a
function with //-style
On Wed, Dec 26, 2018, at 13:23, Sylvain Bertrand wrote:
> Since llvm is pure c++ madness and gcc is still far from being one:
> gnu gcc sucks less than clang/llvm. yes, GNU gcc sucks less than BSD
> clang/llvm, wow.
The chosen language is just one "suckless metric". I hold little love
for C++, but
On Tue, Dec 25, 2018, at 10:11, Cág wrote:
> 1. Is there any network utility suite like net-tools or iproute2 but
> sane and active? Or maybe net-tools was forked by somebody?
Usually the stuff you want to do with these tools are limited to just a
few tasks ("connect to wired network", "connect t
Thanks all. Hope you all had a nice Christmas :-) Let me reply to all
the great feedback in a single email:
On Sat, Dec 22, 2018, at 23:26, Jan Bessai wrote:
> You might add that keeping things small is crucial for the described way
> of operating. Otherwise things are impossible to understand for
14 matches
Mail list logo