Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #69255

Re: Python language hack for C-style programmers [DO NOT USE!] :-)

References <20140327110856.14991bb0@bigbox.christie.dr> <CAPTjJmoSEiBEO9fXfwM7mGywty+dT8erBqeu2mpyrxAf12udcw@mail.gmail.com> <lh2jsg$cqu$1@ger.gmane.org> <CAPTjJmoU-Aa_Y2DDHzCyzMNUfNnuV2i2gsHWZP3gKBhzrXjLzw@mail.gmail.com> <lh39cc$6cd$1@ger.gmane.org>
Date 2014-03-28 18:51 +1100
Subject Re: Python language hack for C-style programmers [DO NOT USE!] :-)
From Chris Angelico <rosuav@gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.8659.1395993082.18130.python-list@python.org> (permalink)

Show all headers | View raw


On Fri, Mar 28, 2014 at 6:46 PM, Peter Otten <__peter__@web.de> wrote:
> Why would you guess if you can check? Just fire up the interactive
> interpreter^W^W compiler:

Partly because there's a difference between valid C++ and valid input
to the G++ compiler :) Knowing that it works with g++ doesn't tell me
that it's actually valid, and I don't feel like digging into the specs
to find out where you're guaranteed to be allowed to do that. (I could
probably test it with one of the language spec options, but then it
still depends on the exact version of GCC and the exact spec chosen.)

ChrisA

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread


Thread

Re: Python language hack for C-style programmers [DO NOT USE!] :-) Chris Angelico <rosuav@gmail.com> - 2014-03-28 18:51 +1100

csiph-web