Net.ObjectDays 2005 Ð Call for Papers
Net.ObjectDays 2005 Ð Call for Papers Erfurt, Germany, September 19-22 www.netobjectdays.org Net.ObjectDays is one of the major international conferences on object-oriented and Internet-based technologies, concepts, and applications. Based on its strong focus on research and innovation, Net.ObjectDays aims at bringing together leading researchers from academia and system architects, developers, and customers from industry and administration. Recent developments in Information and Communication Technologies have substantially changed the nature of global relationships, sources of competitive advantage, and opportunities for economic and social development. These changes pose increasingly complex challenges to the computer science community in general and the software community in particular. Self-adaptation, self-management, and self-healing are key features in a new software landscape that aims on providing flexible solutions to solve one-of-a-kind problems in an adequate, reliable and cost-effective way. Given this background, the focus of Net.ObjectDays 2005 is on methods, models, languages, and tools for efficient, reliable and adaptive composition of software artefacts to provide a scientific and technological foundation allowing for new differentiators such as on-demand computing, situation-aware services, attentive user interfaces. The topics of the conference include but are not limited to: - Object-oriented concepts, languages and technologies - Aspect-oriented software development - Adaptive and reflective languages and systems - Domain-oriented programming - Generative programming - Novel Web applications and interface - Service specification and composition - Process modelling and execution - Grid services infrastructure - Autonomic and on-demand computing - Object-oriented and peer-to-peer middleware - Architecture-centric development - Dynamic software evolution - Software maintenance and reengineering - Component-based approaches - Domain engineering and software product lines We invite original contributions from the above-mentioned areas that neither have been published previously nor are under review by other refereed events or publications. Proceedings of Net.ObjectDays 2005 will be published as Springer LNCS Lecture Notes in Computer Science. Papers will be submitted electronically at www.dcl.hpi.uni-potsdam.de/node2005 in PDF format. Papers must not exceed 16 pages and should be formatted according to the author instructions of Springer-Verlag to be found at www.springer.de/comp/lncs/authors.html All submissions have to be in English. The title page must contain a short abstract and a classification of the topics covered, preferably based on the ones listed above. The paper must clearly state the problem being addressed, the goal of the work, the results achieved, and the relation to previous work. Important dates: Submission of papers: April 24, 2005 Notification: June 03, 2005 Final version due: June 24, 2005 Conference: September 19-22, 2005 Program committee co-chairs: Robert Hirschfeld DoCoMo Euro-Labs, Germany Landsberger Str. 312 80687 MŸnchen, Germany [EMAIL PROTECTED] Andreas Polze HPI at University of Potsdam Prof.-Dr.-Helmert-Stra§e 2-3 14482 Potsdam, Germany [EMAIL PROTECTED] Mathias Weske HPI at University of Potsdam Prof.-Dr.-Helmert-Stra§e 2-3 14482 Potsdam, Germany [EMAIL PROTECTED] -- ___,,,^..^,,, Eliot Miranda Smalltalk - Scene not herd -- http://mail.python.org/mailman/listinfo/python-list
Re: What is a type error?
> Chris Smith wrote: >>I suspect you'll see the Smalltalk version of the objections raised in >>response to my post earlier. In other words, whatever terminology you >>think is consistent, you'll probably have a tough time convincing >>Smalltalkers to stop saying "type" if they did before. If you exclude >>"message not understood" as a type error, then I think you're excluding >>type errors from Smalltalk entirely, which contradicts the psychological >>understanding again. > Chris Uppal wrote: > > Taking Smalltalk /specifically/, there is a definite sense in which it is > typeless -- or trivially typed -- in that in that language there are no[*] > operations which are forbidden[**], Come one Chris U. One has to distinguish an attempt to invoke an operation with it being carried out. There is nothing in Smalltalk to stop one attempting to invoke any "operation" on any object. But one can only actually carry-out operations on objects that implement them. So, apart from the argument about inadvertent operation name overloading (which is important, but avoidable), Smalltalk is in fact strongly-typed, but not statically strongly-typed. -- ___,,,^..^,,, Eliot Miranda Smalltalk - Scene not herd -- http://mail.python.org/mailman/listinfo/python-list
Re: What is a type error?
Darren New wrote: > Eliot Miranda wrote: > >> can only actually carry-out operations on objects that implement them. > > > Execpt that every operation is implemented by every object in Smalltalk. No they are not. Objects implement the methods defined by their class and (inherit) those implemented by the class's superclasses. Note that classes do _not_ have to inherit from Object, and so one can create classes that implement no methods at all. It is a common idiom to create a class that implements two methods, an initialization method and a doesNotUnderstand: method, so create a transparent proxy that intercepts any and all messages sent to it other than the initialization method (*). [(*) With suitable hackery (since Smalltalk gives access to the execution stack through thisContext) one can also invoke doesNotUnderstand: if the initialization message is sent from any object other than the class.] > Unless you specify otherwise, the implementation of every method is to > call the receiver with doesNotUnderstand. (I don't recall whether the > class of nil has a special rule for this or whether it implements > doesNotUnderstand and invokes the appropriate "don't send messages to > nil" method.) No. The run-time error of trying to invoke an operation that isn't implemented by an object is to send the doesNotUnderstand: message. This is another attempt to invoke an operation, i.e. whatever the object's doesNotUnderstand: method is, if any. If the object doesn't implement doesNotUnderstand:, which is quite possible, then the system, will likely crash (either with an out of memory error as it goes into infinite recursion) or hang (looping attempting to find an implementation of doesNotUnderstand:). > There are a number of Smalltalk extensions, such as > multiple-inheritance, that rely on implementing doesNotUnderstand. Which has nothing to do with the separation between message send and method invocation, or the fact that doesNotUnderstand: is a message send, not a hard call of a given doesNotUnderstand: method. -- ___,,,^..^,,, Eliot Miranda Smalltalk - Scene not herd -- http://mail.python.org/mailman/listinfo/python-list
