This is the mail archive of the guile@sourceware.cygnus.com mailing list for the Guile project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: should GOOPS be built-in?

To: Valentin Kamyshenko <val at kamysh dot materials dot kiev dot ua>
Subject: Re: should GOOPS be built-in?
From: Mikael Djurfeldt <mdj at mdj dot nada dot kth dot se>
Date: 13 Dec 1999 00:49:44 +0100
Cc: guile at sourceware dot cygnus dot com
Cc: djurfeldt at nada dot kth dot se
References: <19991208083704.D189B5E79F@sith.bbb.caltech.edu> <87u2lrlssc.fsf@zagadka.ping.de> <hhaenjwynm.fsf@forcix.burse.uni-hamburg.de> <xy7bt7zzhoh.fsf@mdj.nada.kth.se> <m2d7sfcwzl.fsf@kamysh.materials.kiev.ua>

Valentin Kamyshenko <val@kamysh.materials.kiev.ua> writes:

> 	1. Are there available any examples of GOOPS programming "at
> the C level"?

Yes.  It's included in the goops source tree: fdi.c.  You get it
compiled into GOOPS by configuring with --enable-fdi-example.

This C interface is just experimental, though.

> 	2. Where can I find a description of MOP (there is no
> reference in the GOOPS manual)? 

Gregor Kiczales' "The art of the metaobject protocol" is excellent.

Also, since GOOPS is very similar to (and based upon) STk, the Doc
directory in the STk distribution is relevant.

/mdj

Follow-Ups:
- Re: should GOOPS be built-in?
  - From: Lalo Martins

References:
- should GOOPS be built-in?
  - From: Michael Vanier
- Re: should GOOPS be built-in?
  - From: Marius Vollmer
- Re: should GOOPS be built-in?
  - From: forcer
- Re: should GOOPS be built-in?
  - From: Mikael Djurfeldt
- Re: should GOOPS be built-in?
  - From: Valentin Kamyshenko

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]