public inbox for
 help / color / mirror / Atom feed
From: Daniel Skarda <>
Subject: setters and exclamation mark
Date: Fri, 03 Jan 2003 00:00:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Mail Delivery Service's message of "Fri, 3 Jan 2003 00:52:41 +0100")


  current GtkAdjustment patch posted last year (err, few days ago) revealed
guile-gtk naming inconsistency: There are many Gtk functions, one could call 
setters (-set-blahblahblah), but wrappers for these functions does NOT have
exclamation mark. On the other hand, emit-field-accessors (build-guile-gtk)
appends `!' to emitted setters.

  We can:

    1) Forget scheme naming conventions and remove `!' from created setters
       (this change would break NOT any code since setter feature has not been
       used at all)

    2) Add setter hint to define-function, which would mark function as a
       setter and build-guile-gtk would add ending `!' to such functions.

  I think everybody can imagine tedious work on second way (examine all
functions and mark all setters). Since exclamation mark should be used
uniformly, change could break a lot of code.

  So if nobody objects, I say good-bye exclamation mark and choose first way.


       reply	other threads:[~2003-01-03  0:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2003-01-03  0:00 ` Daniel Skarda [this message]
2003-01-03  0:56   ` Kevin Ryde

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).