зеркало из https://github.com/mono/mail-archives.git
79 строки
3.0 KiB
HTML
79 строки
3.0 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||
|
|
<HTML>
|
||
|
|
<HEAD>
|
||
|
|
<TITLE> [Gtk-sharp-list] API Freeze Policy Adjustment
|
||
|
|
</TITLE>
|
||
|
|
<LINK REL="Index" HREF="index.html" >
|
||
|
|
<LINK REL="made" HREF="mailto:jonpryor%40vt.edu">
|
||
|
|
<META NAME="robots" CONTENT="index,nofollow">
|
||
|
|
|
||
|
|
<LINK REL="Previous" HREF="004331.html">
|
||
|
|
<LINK REL="Next" HREF="004335.html">
|
||
|
|
</HEAD>
|
||
|
|
<BODY BGCOLOR="#ffffff">
|
||
|
|
<H1>[Gtk-sharp-list] API Freeze Policy Adjustment
|
||
|
|
</H1>
|
||
|
|
<B>Jonathan Pryor
|
||
|
|
</B>
|
||
|
|
<A HREF="mailto:jonpryor%40vt.edu"
|
||
|
|
TITLE="[Gtk-sharp-list] API Freeze Policy Adjustment">jonpryor@vt.edu
|
||
|
|
</A><BR>
|
||
|
|
<I>Thu, 01 Jul 2004 14:36:33 -0400</I>
|
||
|
|
<P><UL>
|
||
|
|
<LI> Previous message: <A HREF="004331.html">[Gtk-sharp-list] API Freeze Policy Adjustment
|
||
|
|
</A></li>
|
||
|
|
<LI> Next message: <A HREF="004335.html">[Gtk-sharp-list] API Freeze Policy Adjustment
|
||
|
|
</A></li>
|
||
|
|
<LI> <B>Messages sorted by:</B>
|
||
|
|
<a href="date.html#4334">[ date ]</a>
|
||
|
|
<a href="thread.html#4334">[ thread ]</a>
|
||
|
|
<a href="subject.html#4334">[ subject ]</a>
|
||
|
|
<a href="author.html#4334">[ author ]</a>
|
||
|
|
</LI>
|
||
|
|
</UL>
|
||
|
|
<HR>
|
||
|
|
<!--beginarticle-->
|
||
|
|
<PRE>On Thu, 2004-07-01 at 11:20, Murray Cumming wrote:
|
||
|
|
<snip what="guidelines..."/>
|
||
|
|
><i> However, I break these rules sometimes myself in gtkmm, though very
|
||
|
|
</I>><i> rarely. I probably shouldn't. For instance,
|
||
|
|
</I>><i> a) In a stable branch, I have made very small changes to API to make
|
||
|
|
</I>><i> that API usable, when we have made some simple but embarassing mistake.
|
||
|
|
</I>
|
||
|
|
My interpretation of Mike Kestner's statements follows this line of
|
||
|
|
reasoning. He even provides the perfect example:
|
||
|
|
|
||
|
|
><i> > However, if a parameter is really an int[], but the generator has
|
||
|
|
</I>><i> > produced an "out int" parameter (as is the default case for an int*
|
||
|
|
</I>><i> > parameter that has not been marked as an array with metadata), there is
|
||
|
|
</I>><i> > no way to use such a method with the out int semantic. Anybody that
|
||
|
|
</I>><i> > would try to use it as such would quickly find out that it doesn't work,
|
||
|
|
</I>><i> > and would probably be filing a bug report.
|
||
|
|
</I>
|
||
|
|
If the choice is between waiting (at most) 6 months for an API fix (for
|
||
|
|
the next stable release) or waiting a few days to a few weeks for a
|
||
|
|
point-release, I'll take the point release. I suspect most developers
|
||
|
|
would agree.
|
||
|
|
|
||
|
|
- Jon
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</PRE>
|
||
|
|
<!--endarticle-->
|
||
|
|
<HR>
|
||
|
|
<P><UL>
|
||
|
|
<!--threads-->
|
||
|
|
<LI> Previous message: <A HREF="004331.html">[Gtk-sharp-list] API Freeze Policy Adjustment
|
||
|
|
</A></li>
|
||
|
|
<LI> Next message: <A HREF="004335.html">[Gtk-sharp-list] API Freeze Policy Adjustment
|
||
|
|
</A></li>
|
||
|
|
<LI> <B>Messages sorted by:</B>
|
||
|
|
<a href="date.html#4334">[ date ]</a>
|
||
|
|
<a href="thread.html#4334">[ thread ]</a>
|
||
|
|
<a href="subject.html#4334">[ subject ]</a>
|
||
|
|
<a href="author.html#4334">[ author ]</a>
|
||
|
|
</LI>
|
||
|
|
</UL>
|
||
|
|
</body></html>
|