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


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

Re: How security holes happen

Started byMark Lawrence <breamoreboy@yahoo.co.uk>
First post2014-03-03 22:50 +0000
Last post2014-03-03 22:50 +0000
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 Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-03-03 22:50 +0000

#67611 — Re: How security holes happen

FromMark Lawrence <breamoreboy@yahoo.co.uk>
Date2014-03-03 22:50 +0000
SubjectRe: How security holes happen
Message-ID<mailman.7677.1393887042.18130.python-list@python.org>
On 03/03/2014 22:25, Chris Angelico wrote:
> 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
>

Or write every language in Applescript which has 42 not very obvious 
ways of doing each and everything.

-- 
My fellow Pythonistas, ask not what our language can do for you, ask 
what you can do for our language.

Mark Lawrence

---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com

[toc] | [standalone]


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


csiph-web