Optional compilation flag to disable the property functionality?

Taesoo Kwon <[email protected]>
Newsgroups gmane.comp.lang.lua.bind.user
Message-ID <[email protected]>
I have been using luabind for a few years, and cannot implement any
C++ binding without it.
Recently, I read about the discussions about the design difference
between OOLUA and luabind,
and realized that the nice "property" functionality comes at a cost of
having to wait twice as much for every member function/variable
look-up.
(The reason is that __index function calls into C++ to support "properties".)
So I wonder if it would be possible to add optional compilation flag
to disable the property functionality of LUABIND and bypass the
luabind's custom implementation of __index function?

p.s.
I also realized that this applies to luabind's class method too.
For example, member lookups of
class 'ASDF'
is twice as slow as the same class implemented using metatable.
I understand that in some cases, table look-ups can be avoided by
modifying, for example,

  for ...
    x:f()
  end

as

  local f = x.f
  for ...
    f(x)
  end

------------------------------------------------------------------------------
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.