This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: Guile naming conventions
- To: Mikael Djurfeldt <mdj at mdj dot nada dot kth dot se>
- Subject: Re: Guile naming conventions
- From: Jost Boekemeier <jostobfe at linux dot zrz dot TU-Berlin dot DE>
- Date: 01 Apr 2000 10:18:55 +0200
- Cc: jimb at red-bean dot com, guile at sourceware dot cygnus dot com, djurfeldt at nada dot kth dot se
- References: <Pine.LNX.4.21.0003301135130.20677-100000@marvin.ida.ing.tu-bs.de> <xy73dp8lkgr.fsf@mdj.nada.kth.se> <p2t8zyzw0sj.fsf@apfel.zrz.tu-berlin.de> <xy7aejfvsh1.fsf@mdj.nada.kth.se> <p2t4s9mx3ui.fsf_-_@apfel.zrz.tu-berlin.de> <xy7og7uoiwm.fsf@mdj.nada.kth.se>
Mikael Djurfeldt <mdj@mdj.nada.kth.se> writes:
> Jost Boekemeier <jostobfe@calvados.zrz.TU-Berlin.DE> writes:
>
> > Consequence:
> >
> > We must either change the environment proposal to meet the convention
> > that guile currently uses
>
> [...]
>
> > or we should change guile's naming conventions.
>
> Yes. As various people, especially Dirk, has discussed, it would be
> very good to establish clear principles for naming in Guile.
>
> But establishing such a convention has big consequences, so it should
> be done with good consideration.
I beg your pardon but the <type>-set-<element>! convention was
introduced with Jim's proposal. We're talking about an interface
which has been specified last year and which -- if I remember
correctly -- everyone agreed upon.
We are not talking about old code, which can (and should) stay as it is.
We're talking about new code and how newly introduced names should
look like; that was Michael's question.
Jost