[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [patch] initializing parted from an application
From: |
Andrew Clausen |
Subject: |
Re: [patch] initializing parted from an application |
Date: |
Thu, 16 Aug 2001 20:58:57 +1000 |
User-agent: |
Mutt/1.2.5i |
On Thu, Aug 16, 2001 at 12:37:49AM +0200, Neal H Walfield wrote:
> Do you mean dlopen and family?
Yeah, that could do it... Come to think of it, this concern is
bogus, because libparted (in it's "partition editing" capacity, anyway)
won't ever be on an initrd, or anything like that, so there will always
be a backing store...
> As initialization is really about allocating a few data strutures, I do
> not think that this is an issue. But, if you want to look at
> pathological cases, sure, you have a point.
libparted doesn't leak in theory, hehe. And, the PedDevice list &
friends should be very small.
So, I have no objections to using constructors / destructors.
PPL can play games with dlopen (or add their own constructors) if
they have problems with it.
So, to implement this, it's a matter of making ped_init():
static void
_init() __attribute__ ((constructor))
{
...
}
I did that.
Andrew
- [patch] initializing parted from an application, Neal H Walfield, 2001/08/14
- Re: [patch] initializing parted from an application, Andrew Clausen, 2001/08/15
- Re: [patch] initializing parted from an application, Neal H Walfield, 2001/08/15
- Re: [patch] initializing parted from an application, Andrew Clausen, 2001/08/15
- Re: [patch] initializing parted from an application, Neal H Walfield, 2001/08/15
- Re: [patch] initializing parted from an application,
Andrew Clausen <=
- Re: [patch] initializing parted from an application, Neal H Walfield, 2001/08/16
- Re: [patch] initializing parted from an application, Neal H Walfield, 2001/08/16
- Re: [patch] initializing parted from an application, Andrew Clausen, 2001/08/17