On Thu, 19 Jan 2006 17:42:40 -0000 Grant Edwards <[EMAIL PROTECTED]> wrote:
> On 2006-01-19, Fredrik Lundh <[EMAIL PROTECTED]> > wrote: > > >> > It is precisely this power that makes C such a > >dangerous > > language to program in -- it's what makes > >it so easy to crash > > your program, any other program > >running on the same machine, > > >> Nonsense. Under Windows 3.0 that may be true, but on > >any real > OS, you can't "crash any other program running > >on the same > machien" in C, assembly, Python, or Lisp. > > > > given that it's trivial to create fork bombs and memory > > monsters in all those languages, I think you might need > > to define the term "real OS". > > > > (or do you run all your programs in a virtual sandbox ?) > > I guess I never called that sort of DOS attack "crashing" > another program. If that's the sort of think he's talking > about, those are just as trivial to do do in Python as > they are in C. But you do agree that you can shoot your dog in the foot with it, though, I take it? ;-) Yes, true multitasking operating systems and CPUs that support them with protected memory spaces are a good thing. My C experience mostly dates from machines that didn't have those features. Cheers, Terry -- Terry Hancock ([EMAIL PROTECTED]) Anansi Spaceworks http://www.AnansiSpaceworks.com -- http://mail.python.org/mailman/listinfo/python-list
