On Sep 10, 8:07 am, TheFlyingDutchman <[EMAIL PROTECTED]> wrote:
> On Sep 9, 11:20 pm, TheFlyingDutchman <[EMAIL PROTECTED]> wrote:
>
> > It may be that a language that doesn't have a statement terminator
> > (which can be end-of-line) needs a statement continuation symbol.
> > (Excluding languages
On Monday, Sep 10th 2007 at 08:34 -, quoth Marc 'BlackJack' Rintsch:
=>On Mon, 10 Sep 2007 20:19:08 +1200, Lawrence D'Oliveiro wrote:
=>
=>> In message <[EMAIL PROTECTED]>, Marc 'BlackJack' Rintsch
=>> wrote:
=>>
=>>> I see a tree structure here ...
=>>
=>> Good, you're improving.
=>
=>Thank
On Sep 8, 11:16 pm, Lawrence D'Oliveiro <[EMAIL PROTECTED]
central.gen.new_zealand> wrote:
> The one thing I don't like about Python syntax is using backslashes to
> continue lines. Yes, you can avoid them if you can include parentheses
> somehow, but this isn't always possible.
>
> Possible:
>
>
On Sep 10, 4:45 am, Bjoern Schliessmann wrote:
> TheFlyingDutchman wrote:
> > It may be that a language that doesn't have a statement terminator
> > (which can be end-of-line) needs a statement continuation symbol.
>
> Which language could that be? I can hardly imagine making a complex
> program o
On Sep 9, 11:20 pm, TheFlyingDutchman <[EMAIL PROTECTED]> wrote:
> It may be that a language that doesn't have a statement terminator
> (which can be end-of-line) needs a statement continuation symbol.
> (Excluding languages like Lisp that have parentheses everywhere).
Actually I guess Python does
Lawrence D'Oliveiro wrote:
> In message <[EMAIL PROTECTED]>, Marc 'BlackJack'
>> I see a tree structure here ...
>
> Good, you're improving.
Tree structures can't, IMHO, be called two-dimensional. Although,
you can represent them with a two-dimensional graph. If the tree
gets more complex this c
TheFlyingDutchman wrote:
> It may be that a language that doesn't have a statement terminator
> (which can be end-of-line) needs a statement continuation symbol.
Which language could that be? I can hardly imagine making a complex
program out of one statement.
Regards,
Björn
--
BOFH excuse #1
Gabriel Genellina wrote:
> Do you know the Befunge language? Program flow is not lineal but
> along a 2D grid. There are variants over toroids and more bizarre
> surfaces, even using 3D.
Ah, I remember. Once read about it. Really cool idea :)
Regards,
Björn
--
BOFH excuse #149:
Dew on the te
Lawrence D'Oliveiro wrote:
> In message <[EMAIL PROTECTED]>, Bjoern
>> What's wrong with this:
>>
>> for Link in GetEachRecord(
>
> Then you're no longer showing the syntax structure in two
> dimensions.
Why should I want to? :)
BTW, this is the first time I read about "two dimensional syntax
J. Cliff Dyer wrote:
Lawrence D'Oliveiro wrote:
In message <[EMAIL PROTECTED]>, Bjoern Schliessmann wrote:
What's wrong with this:
for Link in GetEachRecord(
Then you're no longer showing the syntax structure in two dimensions.
If somebody handed me a program of more than twenty
Stefan Behnel <[EMAIL PROTECTED]> wrote:
> This actually sounds somewhat pointless to me. If complex things don't
> fit into one line, a good way to deal with it is not to insist on
> making them a single statement.
>
Or make them into a single method/function call. I would post some pseudo-
cod
On 9 sep, 08:14, Bjoern Schliessmann wrote:
> How can a statement be two-dimensional? Like a two-dimensionalTuringMachine?
Do you know the Befunge language? Program flow is not lineal but along
a 2D grid. There are variants over toroids and more bizarre surfaces,
even using 3D.
"Befunge is beli
Lawrence D'Oliveiro wrote:
> In message <[EMAIL PROTECTED]>, Marc 'BlackJack' Rintsch
> wrote:
>> And this is also easily written that way in Python if you don't insist on
>> the line break after the ``if`` or can live with backslashes.
>
> Which is precisely the point.
This actually sounds somew
On Mon, 10 Sep 2007 20:19:08 +1200, Lawrence D'Oliveiro wrote:
> In message <[EMAIL PROTECTED]>, Marc 'BlackJack' Rintsch
> wrote:
>
>> I see a tree structure here ...
>
> Good, you're improving.
Thanks.
>> ... but still no table.
>
> Who said anything about a table?
Me. If that statement i
In message <[EMAIL PROTECTED]>, Marc 'BlackJack' Rintsch
wrote:
> I see a tree structure here ...
Good, you're improving.
> ... but still no table.
Who said anything about a table?
> And this is also easily written that way in Python if you don't insist on
> the line break after the ``if`` or
On Mon, 10 Sep 2007 19:54:49 +1200, Lawrence D'Oliveiro wrote:
> In message <[EMAIL PROTECTED]>, Marc 'BlackJack' Rintsch
> wrote:
>
>> On Mon, 10 Sep 2007 15:02:58 +1200, Lawrence D'Oliveiro wrote:
>>
>>> In message <[EMAIL PROTECTED]>, Bjoern Schliessmann
>>> wrote:
>>>
Lawrence D'Olivei
In message <[EMAIL PROTECTED]>, Marc 'BlackJack' Rintsch
wrote:
> On Mon, 10 Sep 2007 15:02:58 +1200, Lawrence D'Oliveiro wrote:
>
>> In message <[EMAIL PROTECTED]>, Bjoern Schliessmann
>> wrote:
>>
>>> Lawrence D'Oliveiro wrote:
But then you can no longer use indentation to display the
>>>
On Mon, 10 Sep 2007 15:02:58 +1200, Lawrence D'Oliveiro wrote:
> In message <[EMAIL PROTECTED]>, Bjoern Schliessmann wrote:
>
>> Lawrence D'Oliveiro wrote:
>>> But then you can no longer use indentation to display the
>>> two-dimensional structure of the statement.
>>
>> How can a statement be t
It may be that a language that doesn't have a statement terminator
(which can be end-of-line) needs a statement continuation symbol.
(Excluding languages like Lisp that have parentheses everywhere).
--
http://mail.python.org/mailman/listinfo/python-list
In message <[EMAIL PROTECTED]>, Bjoern Schliessmann wrote:
> Lawrence D'Oliveiro wrote:
>> But then you can no longer use indentation to display the
>> two-dimensional structure of the statement.
>
> How can a statement be two-dimensional?
Like this (from C++ code, but the idea is the same):
In message <[EMAIL PROTECTED]>, Bjoern Schliessmann wrote:
> What's wrong with this:
>
> for Link in GetEachRecord(
Then you're no longer showing the syntax structure in two dimensions.
--
http://mail.python.org/mailman/listinfo/python-list
James Stroud wrote:
> Lawrence D'Oliveiro wrote:
>
>> The one thing I don't like about Python syntax is using backslashes to
>> continue lines. Yes, you can avoid them if you can include parentheses
>> somehow, but this isn't always possible.
>>
>> Possible:
>>
>> if (
>> quittin
Lawrence D'Oliveiro wrote:
> The one thing I don't like about Python syntax is using backslashes to
> continue lines. Yes, you can avoid them if you can include parentheses
> somehow, but this isn't always possible.
>
> Possible:
>
> if (
> quitting
> and
> len
Steven D'Aprano wrote:
> That is quite possibly the ugliest piece of code I've ever seen in
> Python. I'm impressed. Did you format it yourself or did you use a
> professionally written code-uglifier?
>
Boy did that make me laugh! The notion of a "code uglifier" just is a
pearl. (I hate to call
Lawrence D'Oliveiro wrote:
> But then you can no longer use indentation to display the
> two-dimensional structure of the statement.
How can a statement be two-dimensional? Like a two-dimensional
Turing Machine?
Regards,
Björn
--
BOFH excuse #156:
Zombie processes haunting the computer
--
Lawrence D'Oliveiro wrote:
> In message <[EMAIL PROTECTED]>, Stefan Behnel wrote:
>
>> He means he has to use backslashes instead of parentheses here.
>>
>> Which is not true, you could easily rephrase this as:
>>
>> for link in GetEachRecord(
>> "links",
>> ):
>>
Steven D'Aprano <[EMAIL PROTECTED]> wrote:
> On Sun, 09 Sep 2007 17:16:05 +1200, Lawrence D'Oliveiro wrote:
>
>> The one thing I don't like about Python syntax is using backslashes to
>> continue lines.
>
> Then don't use them. Put everything in one long line.
>
> Or do something like this. Ins
m_episode"]}),
> Link["from_episode"]
> )
> )
> #end for
IMHO, that's no Python syntax wart, but a coding style wart.
What's wrong with this:
for Link in GetEachRecord(
"links",
(&qu
On Sun, 09 Sep 2007 17:16:05 +1200, Lawrence D'Oliveiro wrote:
> The one thing I don't like about Python syntax is using backslashes to
> continue lines.
Then don't use them. Put everything in one long line.
Or do something like this. Instead of
for Link in GetEachRecord("lots", "and", "lots",
On Sun, 09 Sep 2007 17:16:05 +1200, Lawrence D'Oliveiro wrote:
> The one thing I don't like about Python syntax is using backslashes to
> continue lines. Yes, you can avoid them if you can include parentheses
> somehow, but this isn't always possible.
>
> Possible:
>
> if (
> qui
In message <[EMAIL PROTECTED]>, Stefan Behnel wrote:
> He means he has to use backslashes instead of parentheses here.
>
> Which is not true, you could easily rephrase this as:
>
> for link in GetEachRecord(
> "links",
> ):
> out.write(
> ..
Marc 'BlackJack' Rintsch wrote:
> On Sun, 09 Sep 2007 17:16:05 +1200, Lawrence D'Oliveiro wrote:
>
>> The one thing I don't like about Python syntax is using backslashes to
>> continue lines. Yes, you can avoid them if you can include parentheses
>> somehow, but this isn't always possible.
>>
>> P
On Sun, 09 Sep 2007 17:16:05 +1200, Lawrence D'Oliveiro wrote:
> The one thing I don't like about Python syntax is using backslashes to
> continue lines. Yes, you can avoid them if you can include parentheses
> somehow, but this isn't always possible.
>
> Possible:
>
> […]
>
> Not possible:
>
>
The one thing I don't like about Python syntax is using backslashes to
continue lines. Yes, you can avoid them if you can include parentheses
somehow, but this isn't always possible.
Possible:
if (
quitting
and
len(client["to_write"]) == 0
and
34 matches
Mail list logo
