search for: set_attr

...(Qmf::SchemaArgument.new("vm", Qmf::TYPE_REF, :desc => "Newly created domain object id.", :dir => Qmf::DIR_OUT)) + @ovirt_class.add_method(method) + + @agent.register_class(@ovirt_class) + end + + def start + @ovirt = Qmf::QmfObject.new(@ovirt_class) + @ovirt.set_attr("version", "0.0.0.1") + + obj_id = @agent.alloc_object_id(1, Ovirt::TABLE_ID) + @ovirt.set_object_id(obj_id) + end + + def implement_id_query(context, id) + if id == 1 + # This class is a singleton so it's easy.. :) + @agent.query_response(context, @ovir...

...# This wraps correctly, but causes problems because the colour is freed + # when the attribute is reset. + # + # attr_header_like = CalendarDateAttr.new(BLUE, LIGHT_GREY) </ins><span class="cx"> </span><span class="cx"> @calendar.set_attr(17, attr_red_circle) </span><span class="cx"> @calendar.set_attr(29, attr_green_square) </span><del>-# @calendar.set_attr(13, attr_header_like) </del><ins>+ # @calendar.set_attr(13, attr_header_like) </ins><span class="cx&qu...

On Thursday 21 April 2005 18:28, Vyacheslav Akhmechet wrote: > Evan, > > The problem is that I do not know the type of a target function at > compile time. If you consider my code example, I don't know the type > of 'i' until runtime (in fact, I can't even know a possible range of > types 'i' may assume). But... in a dynamic language each variable must

>> >> If any ARM/GCC experts know how to fix arm.md to not refer to >> Darwin-specific macros, that would be great, too. > > Probably the right general idea is to #define MACHO_DYNAMIC_NO_PIC_P > to be 0 for non-Darwin targets. Not sure where to put this so it > will work for both targets (the Darwin definition comes from config/ > darwin.h). I don't

On Mar 12, 2009, at 8:30 AMPDT, Misha Brukman wrote: > > ../../../../src/llvm-gcc4.2-2.5.source/gcc/config/arm/arm.md:4788: > error: ‘MACHO_DYNAMIC_NO_PIC_P’ undeclared here (not in a function) > > This tells me there are some Darwin-specific bits in arm.md which > shouldn't be there (MachO is Mac OS X-specific). I'm using the > attached script

Evan, The problem is that I do not know the type of a target function at compile time. If you consider my code example, I don't know the type of 'i' until runtime (in fact, I can't even know a possible range of types 'i' may assume). Thanks, - Slava. On 4/21/05, Evan Jones <ejones at uwaterloo.ca> wrote: > On Thu, 2005-21-04 at 09:31 -0400, Vyacheslav Akhmechet

...reading SWIG output and headers to make RDoc-ish output. Does anyone have this somewhere? It would be great to supply some rudimentary RDoc with a package. D) I think we can do some things to make the API a bit more Rubyish without having to hack the interface files. Eg. a few lines that alias set_attr, get_attr and is_attr to more ruby-ish attr=(), attr() and attr?(). We can put in better plumbing later ;) E) This is one where we can use help. Suggest we release as source tarball and gems. I''m happy to bundle binaries into platform gems. OS X: Alex. Sean are you able to check on Mact...

This v5 drops a check for attr_set. Versions: v1 -> v2: * Keep temp attrs as read only v2 -> v3: * Code fix-ups: struct and string as const and add return within switch due to fallthrough * Add Signed-off-by to all commits v3 -> v4: * Rever const to struct attribute. Kbuild complains. v4 -> v5: * Drops a check for attr_set in