What are OOP's Jargons and Complexities?
in [Perl]
|
Prev: swift MT940 files
Next: Is there neq for strings?
From: Erik Max Francis on 23 May 2005 16:18 Jonathan Bartlett wrote: > I think you're misreading some of what is being said. I think you're giving the author too much credit. -- Erik Max Francis && max(a)alcyone.com && http://www.alcyone.com/max/ San Jose, CA, USA && 37 20 N 121 53 W && AIM erikmaxfrancis Love is the true price of love. -- George Herbert
From: Kay Schluehr on 23 May 2005 17:15 Xah Lee wrote: > As part of this new syntax and purity, where everything in a program is > of Classes and Objects and Methods, many complex issues and concept > have arisen in OOP. Yes and it is easy to communicate a class which represents some thing determined by object oriented analysis and can be graphed as an element of an UML diagram in your development team. This is simply the state of the art in the IT industry and if FP-people or followers of any other alternative programming style can communicate their concepts and design patterns via type-classes or parentheses as well or better than they will going to lead the dicourse and OO will fall apart. I'm just sceptical that this is going to happen. Kay
From: John W. Kennedy on 23 May 2005 18:15 Xah Lee wrote: > So, a simple code like this in normal languages: > a = "a string"; > b = "another one"; > c = join(a,b); > print c; > > or in lisp style > (set a "a string") > (set b "another one") > (set c (join a b)) > (print c) > > becomes in pure OOP languages: > public class test { > public static void main(String[] args) { > String a = new String("a string"); > String b = new String("another one"); > StringBuffer c = new StringBuffer(40); > c.append(a); c.append(b); > System.out.println(c.toString()); > } > } The actual Java parallel to what you have written above is: String a = "a string"; String b = "another one"; String c = a + b; System.out.println (c); > In the same way, numbers in Java have become a formalization of many > classes: Double, Float, Integer, Long... and each has a bunch of > "methods" to operate or convert from one to the other. Byte, Short, Integer, Long, Char, Float and Double are wrapper classes, which exist chiefly to allow primitive content to be stored in collection classes. byte, short, int, long, char, float, and double are primitives. > Instead of > aNumber = 3; > print aNumber^3; > > In Java the programer needs to master the ins and outs of the several > number classes, and decide which one to use. (and if a program later > needs to change from one type of number to another, it is often > cumbersome.) This has nothing to do with object orientation or classes, but with strong typing, which is important for program verification, and an inescapable necessity for compiling to efficient object code. Strong typing has been a feature of mainstream programming languages since the late 1950's. -- John W. Kennedy "The bright critics assembled in this volume will doubtless show, in their sophisticated and ingenious new ways, that, just as /Pooh/ is suffused with humanism, our humanism itself, at this late date, has become full of /Pooh./" -- Frederick Crews. "Postmodern Pooh", Preface
From: John Bokma on 23 May 2005 19:31 John W. Kennedy wrote: > inescapable necessity for compiling to efficient object code. Strong > typing has been a feature of mainstream programming languages since the > late 1950's. Give Lee another century and he will get there, hopefully :-D. -- John MexIT: http://johnbokma.com/mexit/ personal page: http://johnbokma.com/ Experienced programmer available: http://castleamber.com/ Happy Customers: http://castleamber.com/testimonials.html
From: alex goldman on 23 May 2005 19:54
John W. Kennedy wrote: > Strong > typing has been a feature of mainstream programming languages since the > late 1950's. I'm just curious, what do you mean by /strong/ typing, and which strongly typed languages do you know? |