On Fri, 21 Dec 2001 at 13:23, eric pareja wrote: > As a computer scientist, you should be able to implement the data > structures in any given language, even as low level as you can go. After > all, they are abstractions. Insulating yourself from the hard task of > implementation only removes the experience of working out the data > structures.
Amen. Like I maintain, Data Structures and Algorithms are supposed to be language independent. They're tools, just like programming languages are tools. The only thing we need to learn (aside from using the tool) is what tool to use for what problem. > Java's strength becomes its weakness when used to -teach- or -learn- > data structures. And there we have it. :) Eric Pareja, can you help us poor souls out and somehow allow us to quote you to Dr. Magboo? We should get back to C/C++ in CS123 (Data Structures and Algorithms) ASAP. Perhaps we can talk about this "going back to C/C++" in the ILUG list? Rommel Feria, what are your comments as far as using Java to teach data structures and algorithms? We would really appreciate it if you could join us in the ILUG mailing list as I need as much beef to back me up in a move to drop this forced Java from our CS123 lab classes (CS123 is Data Structures and Algorithms in UP Manila). > In the same manner that we like having access to the source so we know > the insides of a program, implementing data structures using C is > learning what's inside the "black box" of the abstractions that we use > and practically take little notice of. Using C is perhaps the lowest > level one can go in order to keep the comprehension of the data > structure abstractions intact. Assembly language can also be used, but > oftentimes it becomes a hindrance in teaching data structures because > you have to deal with assembly language nits first. I still can't believe Magboo sacrificed our learning data structures and algorithms by forcing us to learn the "Java nits" first. :( > How can one say that one has chosen something when he only knows of one > and no alternatives? Assembly is good. C is good. C++ is good. Python is good. Java is good. LISP is good. Caml is good. And the list goes on. I wish they'd teach us how to choose the right tool for a given problem, instead of forcing us to use the wrong tools. But then who knows what they know? Sometimes I feel like it's the blind leading the blind in UP Manila's CS. Maybe I should've stayed in Bio. At least there I was sure my profs knew their thing. :( --> Jijo -- Federico Sevilla III :: [EMAIL PROTECTED] Network Administrator :: The Leather Collection, Inc. GnuPG Key: http://jijo.leathercollection.ph/jijo.gpg _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
