On Jan 15, 2008 3:35 PM, Gus Wirth <[EMAIL PROTECTED]> wrote: > Mark Schoonover wrote: > > Gus, > > > > On Jan 15, 2008 3:24 PM, Gus Wirth <[EMAIL PROTECTED]> wrote: > > > >> Darren New wrote: > >>> Gus Wirth wrote: > >>>> The programmers of the future won't be using languages that have > >>>> pointers. Look at Java, Python, Perl, TCL/TK (Hi Lan!), PHP, > >>>> Javascript, Erlang, Haskell, Ruby, and many of the other new and > >>>> experimental languages coming out. NONE of the new languages have > >>>> pointers. > >>> Errr, no. Python, Java, Javascript and Ruby all have pointers. > Probably > >>> erlang as well, but I don't know that one yet, and possibly Perl for > >>> some meaning of the word "pointer". Not Haskell or Tcl, because > they're > >>> both value-only languages, in essence. > >> Please explain your concept of a pointer. To me it is a reference to a > >> memory location like in C. As a programmer you can abuse it at will. > >> None of the languages I mentioned meet that definition. > > > > > > Then Perl meets that definition. > > As they say in Missouri, show me. What you are saying is that Perl > allows you to escape the virtual machine and directly reference memory > from the OS, thus causing segfaults when you go to a wrong location. > > Gus > > Well, Perl doesn't segfault. It'll print out the actual memory location in hex to the screen if it hasn't been properly dereferenced.
In your first definition of a pointer, you never mentioned anything about a virtual machine being a requirement for a pointer. -- Mark Schoonover, CMDBA http://www.linkedin.com/in/markschoonover http://marksitblog.blogspot.com [EMAIL PROTECTED] -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
