Xref: utzoo comp.lang.c++:3114 comp.lang.lisp:1701 comp.lang.modula2:1460 comp.lang.prolog:1696 comp.lang.smalltalk:1020 comp.lang.misc:2863
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wasatch!cs.utexas.edu!uunet!ide!wilbury!rai
From: rai@wilbury.uucp (Nitin Rai)
Newsgroups: comp.lang.c++,comp.lang.lisp,comp.lang.modula2,comp.lang.prolog,comp.lang.smalltalk,comp.lang.misc
Subject: Re: C++ vs. Other OOLs
Message-ID: <41@ide.UUCP>
Date: 25 Apr 89 19:30:57 GMT
References: <2602@ssc-vax.UUCP> <5947@pdn.paradyne.com> <1022@quintus.UUCP> <461@esosun.UUCP>
Sender: usenet@ide.COM
Reply-To: rai@wilbury.UUCP (Nitin Rai)
Organization: IDE, San Francisco
Lines: 18

In article <461@esosun.UUCP> kobryn@esosun.UUCP (Cris Kobryn) writes:
>It is more than *possible* to define objects in Prolog.  Consider Quintus'
>ProWINDOWS, an OOPS for UI devlopment:  it supports abstraction, inheritance, 
>polymorphism and message-passing.  (If you need a technical POC at Quintus,
>I'd be glad to oblige ;->)
>
>-- Cris Kobryn

No you are not defining objects in Prolog. ProWINDOWS is a separate process
(C process) and you can create, manipulate and destroy "Objects" defined
in ProWINDOWS through prolog. The objects are ProWINDOWS objects that accessible
through prolog. It doesn't make Quintus Prolog object oriented in any way.

Nitin


{ "If Prolog is god and Warren is its prophet, then O'Keefe is its messiah!:-) }