A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2001-August/016747.html below:

[Python-Dev] '*' instead of 'yield'?

[Python-Dev] '*' instead of 'yield'?Ken Manheimer klm@zope.com
Mon, 6 Aug 2001 18:04:00 -0400 (EDT)
Roman, that was a sensible way to end this particular thread - forgive me
for gratuitously extending it a tiny bit, but i just can't resist...

On Mon, 6 Aug 2001, Roman Suzi wrote:

> [...]
> Or, yes, and next step is to use '?' in place of 'print' ;-)
> 
> from __future__ import parrot
> 
> # must allow for such things:
> 
> = myfun(x, y, z):
>   ? "how are you?"
>   S = 0
>   4 i <- x..y,z:
>     S += i
>   ** S
> 
> = mygen(x):
>   4 k <- 1..x:
>     * k
> 
> ? myfun(1, 3, 5)
> ? mygen(20)

I don't feel this is an, um, balanced example if you leave alone the only
non-expression in python that *is* signalled soley by punctuation, so:

  from __future__ import parrot

  comment must allow for such things: endcomment

  = myfun(x, y, z):
    ? "how are you?"
    S = 0
    4 i <- x..y,z:
      S += i
    ** S
  ...

:)

and-voluntary-block-delimeter-close-would-be-"comment end endcomment"'ly y'rs,

Ken Manheimer
klm@digicool.com




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4