All language issues aside, I think one of the things (that others have
touched on here but I'd like to reiterate) that makes something
suckless is fewer dependencies and less version management.
Due to Python's "batteries included" philosophy and the large amount
of 3rd party libraries often used,
> On 03/03/2014 11:21 PM, Szymon Olewniczak wrote:
> > [a whole load of quoting]
Mind trimming your quotes?
On Mon, Mar 03, 2014 at 11:25:18PM +0100, koneu wrote:
> Isn't Python that white space sensitive crap
How does that have any bearing on sucklessness? It's a separate
argument. Practically
Quoth FRIGN:
> I recently thought about porting portage (written in Python) to C and
> read into its source code.
> Calling it a mess is a compliment, given there are almost no comments
> and lots of deprecated functions.
> Portage is not only an example for quite unmaintainable code, but also
> fo
On Mon, Mar 03, 2014 at 11:21:02PM +0100, Szymon Olewniczak wrote:
> […] I must admit that I've found Python much less harmful that I had
> previously considered it to be.
Do you care about the language or a particular implementation?
For the latter, packaging sucks, it has libraries to deal with
On Mon, 3 Mar 2014 23:28:13 +
sin wrote:
> I don't agree. At the very least have a look at eprintf() from the
> 'The practice of programming'. We are using similar functions in sbase
> and ubase.
In sbase and ubase, this definitely makes sense.
However, what we're dealing with here is a di
On Mon, Mar 03, 2014 at 09:53:20PM +0100, FRIGN wrote:
> On Mon, 3 Mar 2014 21:16:46 +
> sin wrote:
>
> > Why can't we not use err(), warn(), etc. from err.h?
>
> It's not necessary and introduces more problems, as it forces a certain
> format on the error-messages, always beginning with "qu
On Tue, 4 Mar 2014 00:06:19 +0100
v4hn wrote:
> In the end, there a lot of people who learnt to write unmaintainable code.
> I seriously prefer perl-programmers who know what they're doing.
Which brings us back to stali:
I recently thought about porting portage (written in Python) to C and
read
On Mon, Mar 03, 2014 at 09:35:18PM +0100, FRIGN wrote:
> On Mon, 3 Mar 2014 23:21:02 +0100
> Szymon Olewniczak wrote:
> > (...) and I must admit that I've found Python much less
> > harmful that I had previously considered it to be.
>
> I agree on this one. The language designers did a good job.
On Mon, 3 Mar 2014 21:16:46 +
sin wrote:
> Why can't we not use err(), warn(), etc. from err.h?
It's not necessary and introduces more problems, as it forces a certain
format on the error-messages, always beginning with "quark:".
I'm all for using built-in functions, but in this case, it's n
On 03/03/2014 11:21 PM, Szymon Olewniczak wrote:
Hi,
I've recently had a presentation(during local Linux User Group meeting)
about some basic ideas Unix philosophy and suckless projects. This has led
my attention once to the topic of programming languages and I must admit
that I've found Python m
Greetings.
On Mon, 03 Mar 2014 23:31:43 +0100 Szymon Olewniczak
wrote:
> Hi,
> I've recently had a presentation(during local Linux User Group meeting)
> about some basic ideas Unix philosophy and suckless projects. This has led
> my attention once to the topic of programming languages and I mus
On Mon, 3 Mar 2014 23:21:02 +0100
Szymon Olewniczak wrote:
> (...) and I must admit that I've found Python much less
> harmful that I had previously considered it to be.
I agree on this one. The language designers did a good job.
The only _big_ problem I have with it is the fact it's not compil
Hi,
I've recently had a presentation(during local Linux User Group meeting)
about some basic ideas Unix philosophy and suckless projects. This has led
my attention once to the topic of programming languages and I must admit
that I've found Python much less harmful that I had previously
considered
On March 3, 2014 10:16:46 PM CET, sin wrote:
>On Mon, Mar 03, 2014 at 07:39:13PM +0100, FRIGN wrote:
>> I'm currently working on quark and would like to propose a patch
>> simplifying the logmsg-, logerrmsg- and die-functions in quark.
>> There's more to come!
>
>Why can't we not use err(), warn()
On Mon, 3 Mar 2014 22:02:26 +0100
Szabolcs Nagy wrote:
> note that stdlib.h may include math.h which declares log
> with a different type
Thanks, I didn't notice that, as I'm using musl to compile it.
Using glibc:
> quark.c:70:13: warning: conflicting types for built-in
function
On Mon, Mar 03, 2014 at 07:39:13PM +0100, FRIGN wrote:
> I'm currently working on quark and would like to propose a patch
> simplifying the logmsg-, logerrmsg- and die-functions in quark.
> There's more to come!
Why can't we not use err(), warn(), etc. from err.h?
* FRIGN [2014-03-03 19:39:13 +0100]:
> +static void log(int type, const char *errstr, ...);
note that stdlib.h may include math.h which declares log
with a different type
such namespace issues can be fixed by using another name or
#undef log
#define log quark_log
after the header includes an
Good evening,
I'm currently working on quark and would like to propose a patch
simplifying the logmsg-, logerrmsg- and die-functions in quark.
There's more to come!
Cheers
FRIGN
@sin: Now generated with git format-patch ;)
--
FRIGN
>From 77a72d1e41c92b9ddbe6b51f5ac2a7ffecf39c4b Mon Sep 17 00
>From 9fcdca78649a1b7a6f19db4729e621388ad89814 Mon Sep 17 00:00:00 2001
From: sin
Date: Mon, 3 Mar 2014 13:57:30 +
Subject: [PATCH] Fix building on OpenBSD 5.5
getdirentries() has been removed and instead we should use
getdents().
---
lib9/dirread.c | 9 +
1 file changed, 9 insertio
Hi,
This is a fix for 9base to enable building on musl.
>From 8fccc638b7d48702e482b1e1627c8e83770dfa33 Mon Sep 17 00:00:00 2001
From: sin
Date: Mon, 3 Mar 2014 10:59:34 +
Subject: [PATCH] Simplify preprocessor conditions to enable building on
musl-libc
musl-libc does not export __MUSL__ so
20 matches
Mail list logo
