On Sun, 2009-04-12 at 14:55 -0400, Havoc Pennington wrote:
> Hi,
>
> On Sun, Apr 12, 2009 at 9:14 AM, Christian Dywan
> wrote:
> > You are asserting that something like a "gint" or "guint" is not
> > something that can be saved to disk.
>
> I'm not saying that; I'm saying they can only be saved
2009/4/12 A. Walton :
> 2009/4/12 Grzegorz Kuczyński :
>> Very thanks Regards.
>>
>> Ok I understand the idea, but...
>> how work it? for example:
>> ---
>> struct _GtkWindow
>> {
>> GtkBin bin;
>>
>> gchar *GSEAL (title);
>> ---
>> void
>> gtk_window_set_title (GtkWindow
2009/4/12 Grzegorz Kuczyński :
> Very thanks Regards.
>
> Ok I understand the idea, but...
> how work it? for example:
> ---
> struct _GtkWindow
> {
> GtkBin bin;
>
> gchar *GSEAL (title);
> ---
> void
> gtk_window_set_title (GtkWindow *window,
> const gchar
Hi,
On Thu, Apr 9, 2009 at 11:38 AM, Dan Winship wrote:
> So, my feedback is, if the type system is explicitly just D-Bus and
> nothing else, shouldn't it be called "GDBusType" or something? (I'm not
> saying it's *bad* that it's D-Bus-specific, just that it should be more
> explicit about it.)
Hi,
On Sun, Apr 12, 2009 at 9:14 AM, Christian Dywan wrote:
> Using G_TYPE_FOO in the API is imho a lot more agreeable than any new
> string signature. Sure it's more to type, but at the same time it's
> more comprehensible. :)
>
I don't disagree for C. One thing to note though, it isn't really
Hi,
On Sun, Apr 12, 2009 at 9:14 AM, Christian Dywan wrote:
> You are asserting that something like a "gint" or "guint" is not
> something that can be saved to disk.
I'm not saying that; I'm saying they can only be saved to disk by
converting them to a fixed-size integer.
"int" is a bad example
Very thanks Regards.
Ok I understand the idea, but...
how work it? for example:
---
struct _GtkWindow
{
GtkBin bin;
gchar *GSEAL (title);
---
void
gtk_window_set_title (GtkWindow *window,
const gchar *title)
{
char *new_title;
g_return_if_fail (GTK_IS_
Grzegorz Kuczyński a écrit :
> Colomban Wendling pisze:
>> AFAIK, it is used to hide members of GTK+ and GDK structures that
>> will become opaques in future releases (3.0 or so); then it makes
>> easy to see if a source must be updated not to use direct access
>> of members. In practice, compilati
Am Sat, 11 Apr 2009 13:55:36 -0400
schrieb Havoc Pennington :
> Hi,
>
> On Sat, Apr 11, 2009 at 11:06 AM, Matthias Clasen
> wrote:
> >
> > What David is saying (and I'm sure you understood) is that glib
> > already comes with a type system, namely GType. Adding a completely
> > separate one next
