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


Groups > comp.lang.python > #67606 > unrolled thread

Re: How security holes happen

Started byChris Angelico <rosuav@gmail.com>
First post2014-03-04 09:25 +1100
Last post2014-03-04 09:25 +1100
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: How security holes happen Chris Angelico <rosuav@gmail.com> - 2014-03-04 09:25 +1100

#67606 — Re: How security holes happen

FromChris Angelico <rosuav@gmail.com>
Date2014-03-04 09:25 +1100
SubjectRe: How security holes happen
Message-ID<mailman.7674.1393886043.18130.python-list@python.org>
On Tue, Mar 4, 2014 at 9:19 AM, Cameron Simpson <cs@zip.com.au> wrote:
> On 03Mar2014 09:17, Neal Becker <ndbecker2@gmail.com> wrote:
>>  Charles R Harris <charlesr.harris@gmail.com> Wrote in message:
>> >
>>
>> Imo the lesson here is never write in low level c. Use modern
>>  languages with well designed exception handling.
>
> What, and rely on someone else's low level C?

Someone needs to port Python to LISP.

And then write a LISP interpreter in JavaScript.

And an ECMAScript engine in Pike.

And a Pike interpreter in Java.

And a Java run-time written in ActionScript.

It's turtles all the way down...

ChrisA

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web