Displaying 3 results from an estimated 3 matches for "first_pet".
Did you mean:
first_path
2008 May 13
2
[LLVMdev] Python bindings available.
...rn Owner(_core.LLVMCreateOwner(pet.ptr), pet)
def __init__(self, ptr, kid):
self.ptr = ptr
pet.owner = self
def add(self, pet):
if (pet.owner)
raise OwnershipError("Pet already owned!")
_core.LLVMAddPet(pet.ptr)
pet.owner = self
@property
def first_pet(self):
# Create an 'owned' pet.
return Pet(_core.LLVMGetFirstPet(self.ptr), self)
def __del__(self):
_core.LLVMDisposeOwner(pet.owner)
This will create gobs of child->parent references. Don't remember
whether that's a problem in Python. This pattern is comp...
2008 May 13
0
[LLVMdev] Python bindings available.
On Tue, May 13, 2008 at 1:22 PM, Gordon Henriksen
<gordonhenriksen at mac.com> wrote:
> On 2008-05-13, at 02:12, Mahadevan R wrote:
>
> >>> That's not how the object works...
> >
> > Gordon, I think I can make it work if we have the following additional
> > function in LLVM-C:
> >
> > LLVMModuleRef LLVMGetModule(LLVMModuleProviderRef
2008 May 13
2
[LLVMdev] Python bindings available.
On 2008-05-13, at 02:12, Mahadevan R wrote:
>>> That's not how the object works...
>
> Gordon, I think I can make it work if we have the following additional
> function in LLVM-C:
>
> LLVMModuleRef LLVMGetModule(LLVMModuleProviderRef MP) {
> return wrap(unwrap(MP)->getModule());
> }
Can I ask, how general is your solution? I only intended to use this