Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!feeder.erje.net!news.musoftware.de!wum.musoftware.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Gregory Ewing Newsgroups: comp.lang.python Subject: Re: The end to all language wars and the great unity API to come! Date: Sun, 03 Jul 2011 16:06:28 +1200 Lines: 21 Message-ID: <97a866Fa5U1@mid.individual.net> References: <1bf8cf87-b173-470a-a05e-a65616c988a0@d22g2000yqn.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net C8l3CE3AX9XAw1Vb0t3mdwm4X1wigisdggtuhe+1wn72xkcZIp Cancel-Lock: sha1:XGCKtsuv/bM3+zSyf2SYhR5pkrs= User-Agent: Mozilla Thunderbird 1.0.5 (Macintosh/20050711) X-Accept-Language: en-us, en In-Reply-To: Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:8721 Chris Angelico wrote: > Your proposed "Unity API" (which I assume has nothing to do with Natty > Narwhal's preferred interface) already exists. It's the C language. Or maybe GObject Introspection is closer to what you have in mind? A library that supports GI advertises enough information about itself for dynamic languages such as Python and Ruby to automatically construct fairly object-oriented interfaces. It's not perfect, though; for example, the old PyGtk module used to let you access most of what Gtk calls "properties" using Python attribute access, but with GI you have to call the get_property and set_property functions. Also you often can't just call a class to construct an object, but have to call a separate constructor function instead. -- Greg