mail-archives/gtk-sharp-list/2002-June/000097.html

88 строки
3.0 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Gtk-sharp-list] Naming thoughts
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mkestner%40speakeasy.net">
<META NAME="robots" CONTENT="index,nofollow">
<LINK REL="Previous" HREF="000096.html">
<LINK REL="Next" HREF="000098.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Gtk-sharp-list] Naming thoughts
</H1>
<B>Mike Kestner
</B>
<A HREF="mailto:mkestner%40speakeasy.net"
TITLE="[Gtk-sharp-list] Naming thoughts">mkestner@speakeasy.net
</A><BR>
<I>19 Jun 2002 18:27:38 -0500</I>
<P><UL>
<LI> Previous message: <A HREF="000096.html">[Gtk-sharp-list] Naming thoughts
</A></li>
<LI> Next message: <A HREF="000098.html">[Gtk-sharp-list] Gtk#
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#97">[ date ]</a>
<a href="thread.html#97">[ thread ]</a>
<a href="subject.html#97">[ subject ]</a>
<a href="author.html#97">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Wed, 2002-06-19 at 13:17, Rachel Hestilow wrote:
&gt;<i> A fix to the &quot;EmitAdd&quot; problem that doesn't require extensive metadata
</I>&gt;<i> hacking occured to me last night:
</I>&gt;<i>
</I>&gt;<i> As far as I can tell, nearly all[1] of the signal/method collisions in
</I>&gt;<i> which the method truly only emits a signal are void(void) methods. So
</I>&gt;<i> perhaps the resolution process should look like:
</I>&gt;<i>
</I>&gt;<i> a) If the method signature is void(void), prepend &quot;Emit&quot; to the method.
</I>&gt;<i> b) Elsewise, append &quot;Emitted&quot; to the signal.
</I>&gt;<i>
</I>&gt;<i> Thoughts?
</I>
Interesting observation.
I don't like having Emitted on the end of signal names any better than
having Emit on the front of Method names, though it would suck less than
the current solution in some cases (eg the EmitAdd wart).
What I had intended to do was to add a &quot;Collision&quot; class to manually map
the collisions. I think an Add method with an Added signal is nicer than
AddEmitted, for example. This should be a fairly static list of
collisions, so it's not like it will take a ton of maintenance going
forward, and if we put a generation warning when an unresolved collision
is detected, we'll be better prepared to lobby for Gtk+ fixes in new API
additions as they occur.
I don't think this falls into the category of extensive metadata
hacking.
Mike
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI> Previous message: <A HREF="000096.html">[Gtk-sharp-list] Naming thoughts
</A></li>
<LI> Next message: <A HREF="000098.html">[Gtk-sharp-list] Gtk#
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#97">[ date ]</a>
<a href="thread.html#97">[ thread ]</a>
<a href="subject.html#97">[ subject ]</a>
<a href="author.html#97">[ author ]</a>
</LI>
</UL>
</body></html>