On Fri, 2005-12-16 at 15:24 -0800, Shahms King wrote:
> which quite a few of them do. I don't have a compiler to test this on,
> but if GNOME_VFS_FILE_INFO_SET_LOCAL is changed to:
>
> #define GNOME_VFS_FILE_INFO_SET_LOCAL(info, value) \
> ((info)->flags = (value ? \
> ((info)->flags | GNOME_VFS_FILE_FLAGS_LOCAL) : \
> ((info)->flags & ~GNOME_VFS_FILE_FLAGS_LOCAL)))
>
> Does the error go away? The above change shouldn't change the API as the
> macro still returns the new value of flags, but *should* silence the
> warning. If the above works, the rest of the macros should probably be
> changed.
Rodrigo, could you test this? It seems like a better approach if it
works.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Alexander Larsson Red Hat, Inc
[EMAIL PROTECTED] [EMAIL PROTECTED]
He's an ungodly Amish senator with a mysterious suitcase handcuffed to his
arm. She's a manipulative gold-digging magician's assistant on the trail of a
serial killer. They fight crime!
_______________________________________________
gnome-vfs-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gnome-vfs-list
