On 26.07.2017 04:47, Christopher Clements wrote:
My high-school programming class was advertised as teaching people how to
program in C and do all sorts of low-level stuff. I signed up thinking
I might finally meet a "computer expert" that actually knew what they
were talking about...
The teac
On Tue, Jul 25, 2017 at 12:49:17PM +0200, Dr. Nikolaus Klepp wrote:
Am Dienstag, 25. Juli 2017 schrieb Didier Kryn:
> https://around.com/ariane.html
Even with a high level language carefully designed to discourage
loose programming and dirty low-level tricks, it is still possible,
although
On Sun, Jul 23, 2017 at 04:56:56AM -0400, Hendrik Boom wrote:
On Sat, Jul 22, 2017 at 11:26:56PM +0200, Adam Borowski wrote:
On Sat, Jul 22, 2017 at 06:50:19AM +0100, KatolaZ wrote:
> you might probably want to have a look at:
>
> http://popcon.devuan.org/
>
> Whatever the statistical signifi
Le 25/07/2017 à 12:49, Dr. Nikolaus Klepp a écrit :
Am Dienstag, 25. Juli 2017 schrieb Didier Kryn:
https://around.com/ariane.html
Even with a high level language carefully designed to discourage
loose programming and dirty low-level tricks, it is still possible,
although with strong effo
Am Dienstag, 25. Juli 2017 schrieb Didier Kryn:
> > https://around.com/ariane.html
>
> Even with a high level language carefully designed to discourage
> loose programming and dirty low-level tricks, it is still possible,
> although with strong efforts, to fuck the compiler and keep program
Sometimes, though, you *need* to keep doing low-level things. It's not much of
a necessity in the current state of technology anymore, but if you recall back
in the 90s people used to hand-tune assembly code because the C code generated
by the compiler was not efficient enough. The hardware was
Le 25/07/2017 à 00:34, Alessandro Selli a écrit :
On Mon, 24 Jul 2017 at 21:52:23 +0200
Ruediger Meier wrote:
On Monday 24 July 2017, Joachim Fahrner wrote:
Am 2017-07-24 20:34, schrieb Hendrik Boom:
How much source code actually cares whether pointers are 32 or 64
bits?
Clean written code
I was responding to this by Bradley M. Kuhn:
https://lists.debian.org/debian-user/2017/07/msg00811.html
Rather, the giant worldwide queue of known GPL violations
should be prioritized by figuring out which ones, if solved, will do
the
most to maximize software freedom for all users.
Explainin
