Re: [libvirt] [PATCH] __FUNCTION__ is not portable

2008-12-17 Thread Jim Meyering
"Daniel P. Berrange" wrote: > On Tue, Dec 16, 2008 at 06:50:44PM -0800, john.le...@sun.com wrote: >> # HG changeset patch >> # User john.le...@sun.com >> # Date 1229399267 28800 >> # Node ID ee6ccfc062f49f514d7ae8924d5a596b18441fee >> # Parent b105e5a7cd6190e0b952a1587d7e80f39d02e63c >> __FUNCTI

Re: [libvirt] [PATCH] __FUNCTION__ is not portable

2008-12-17 Thread Daniel P. Berrange
On Tue, Dec 16, 2008 at 06:50:44PM -0800, john.le...@sun.com wrote: > # HG changeset patch > # User john.le...@sun.com > # Date 1229399267 28800 > # Node ID ee6ccfc062f49f514d7ae8924d5a596b18441fee > # Parent b105e5a7cd6190e0b952a1587d7e80f39d02e63c > __FUNCTION__ is not portable > > __func__ is.

[libvirt] [PATCH] __FUNCTION__ is not portable

2008-12-16 Thread john . levon
# HG changeset patch # User john.le...@sun.com # Date 1229399267 28800 # Node ID ee6ccfc062f49f514d7ae8924d5a596b18441fee # Parent b105e5a7cd6190e0b952a1587d7e80f39d02e63c __FUNCTION__ is not portable __func__ is. Some places aren't covered by the back-compat define (why is that there?) Signed-o