Peter Hansen wrote:
> Fredrik Lundh wrote:
>
>>Peter Hansen wrote:
>>
>>>Does it really have to be 158 lines to demonstrate these few issues? I
>>>for one almost never take the time to dig through 158 lines of someone
>>>else's code, partly on the assumption that almost any interesting issue
>>>c
Fredrik Lundh wrote:
> Peter Hansen wrote:
>>Does it really have to be 158 lines to demonstrate these few issues? I
>>for one almost never take the time to dig through 158 lines of someone
>>else's code, partly on the assumption that almost any interesting issue
>>can be covered (using Python, spe
Richie Hindle wrote:
> I didn't read every one of his 158 lines, but his code is pure
> poetry, or possibly triple-distilled evil, depending on your point of
> view. 158 lines very well spent either way!
I definitely fall in the "pure evil" camp ;) It's been a while since I
chuckled at code ...
Steve Holden <[EMAIL PROTECTED]> writes:
>> I think you missed the other Peter's second post, where he points to
>> his
>> program: http://www.pick.ucam.org/~ptc24/yvfc.html
>> I didn't read every one of his 158 lines, but his code is pure
>> poetry, or
>> possibly triple-distilled evil, depending
Richie Hindle wrote:
> [Peter]
>
>>Does it really have to be 158 lines to demonstrate these few issues?
>
>
> I think you missed the other Peter's second post, where he points to his
> program: http://www.pick.ucam.org/~ptc24/yvfc.html
>
> I didn't read every one of his 158 lines, but his code
Richie Hindle wrote:
>
> [Peter]
>> Does it really have to be 158 lines to demonstrate these few issues?
>
> I think you missed the other Peter's second post, where he points to
> his program: http://www.pick.ucam.org/~ptc24/yvfc.html
>
> I didn't read every one of his 158 lines, but his code i
[Peter]
> Does it really have to be 158 lines to demonstrate these few issues?
I think you missed the other Peter's second post, where he points to his
program: http://www.pick.ucam.org/~ptc24/yvfc.html
I didn't read every one of his 158 lines, but his code is pure poetry, or
possibly triple-dis
Peter Hansen wrote:
> Does it really have to be 158 lines to demonstrate these few issues? I
> for one almost never take the time to dig through 158 lines of someone
> else's code, partly on the assumption that almost any interesting issue
> can be covered (using Python, specifically) in about a
Peter Corbett wrote:
> I've written a program to illustrate a few... syntactic issues with
> Python. It's 158 <80 character lines long.
>
> About how short should a program be to be postable to this newsgroup -
> in other words, at what length should you stick it on a web page and
> post a link?
[EMAIL PROTECTED] writes:
>
> Peter> About how short should a program be to be postable to this
> Peter> newsgroup - in other words, at what length should you stick it on
> Peter> a web page and post a link?
>
> 158 lines is probably not a killer. However, consider what misbehaving n
Peter> About how short should a program be to be postable to this
Peter> newsgroup - in other words, at what length should you stick it on
Peter> a web page and post a link?
158 lines is probably not a killer. However, consider what misbehaving news
and mail readers are likely to do
11 matches
Mail list logo
