public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Heiko Wundram <heiko@xencon.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT: Python (was: package.keywords syntax?)
Date: Fri, 31 Oct 2008 11:31:16 +0100	[thread overview]
Message-ID: <200810311131.16991.heiko@xencon.net> (raw)
In-Reply-To: <20081031095423.GA8173@aldous>

Am Friday 31 October 2008 10:54:23 schrieb Matthias Bethke:
> Hi Albert,
>
> on Thu, Oct 30, 2008 at 03:11:04PM -0400, you wrote:
> > ... but Jorge is right.  This is easily picked up by a lint tool... and
> > good python programmers use them ;-).  Some python-aware editors even
> > have this functionality built in.
>
> Whow...I've been out of Python long enough to totally forget that you
> *needed* to do this. In Perl, the "use strict" you find at the top of
> every well-written script does it at compile time.

<sarcasm>
Yeah, let's continue to bash Python, which is such a badly broken language 
nobody wants to use it productively, because other languages offer so much 
better functionality to test for programmer error at compile time. Perl is a 
brilliant example to mention in this context.
</sarcasm>

Seriously: dynamic typing is a blessing, (only!) when combined with strict 
typing (where Perl doesn't [really] have the latter, even when use strict is 
in effect). Having to declare variables before use mostly is irrelevant (I'm 
not talking about _defining_ variables before use), because it's no common 
source of bugs.

At least that's my 5 cents.

-- 
Heiko Wundram
hackerkey://v4sw7CHJLSUY$hw5ln5pr7FOP$ck2ma9u7FL$w3DVWXm0l7GL$i65e6t3EMRSXb7ADORen5a26s5MSr2p-6.62/-6.56g5AORZ



  reply	other threads:[~2008-10-31 10:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28 17:07 [gentoo-user] package.keywords syntax? Helmut Jarausch
2008-10-28 17:20 ` Neil Bothwick
2008-10-28 17:22 ` Andrey Vul
2008-10-28 17:39   ` Ricardo Saffi Marques
2008-10-28 17:49     ` Neil Bothwick
2008-10-28 20:29     ` Andrey Vul
2008-10-28 21:01       ` Alan McKinnon
2008-10-28 21:34         ` Jorge Peixoto de Morais Neto
2008-10-28 21:47           ` Robert Bridge
2008-10-28 21:56           ` Alan McKinnon
2008-10-28 22:17             ` Jorge Peixoto de Morais Neto
2008-10-28 22:41               ` Alan McKinnon
2008-10-28 22:55                 ` Jorge Peixoto de Morais Neto
2008-10-29  7:16                   ` Alan McKinnon
2008-10-29 14:16                     ` Andrey Vul
2008-10-29 20:13                     ` Jorge Peixoto de Morais Neto
2008-10-30 10:46                       ` Dirk Uys
2008-10-30 11:00                         ` Dirk Uys
2008-10-30 18:54                           ` Jorge Peixoto de Morais Neto
2008-10-30 19:11                             ` Albert Hopkins
2008-10-31  8:02                               ` Dirk Uys
2008-10-31  9:54                               ` [gentoo-user] OT: Python (was: package.keywords syntax?) Matthias Bethke
2008-10-31 10:31                                 ` Heiko Wundram [this message]
2008-10-30 19:12                         ` [gentoo-user] package.keywords syntax? Jorge Peixoto de Morais Neto
2008-10-31  7:57                           ` Dirk Uys

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200810311131.16991.heiko@xencon.net \
    --to=heiko@xencon.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox