From: Anders Selander <selander@...>
Date: 2002-02-20T02:07:55+09:00
Subject: Re: Rinn and Perl CORBA::ORBit

On Wed, Feb 20, 2002 at 01:18:48AM +0900, Paul Brannan wrote:
> On Wed, Feb 20, 2002 at 01:04:51AM +0900, Anders Selander wrote:
> >   ./client.rb:16: undefined method `name' for #<Rinn::ORBit::Stub:0x40393be8> (NameError)
> I think you need to _narrow your object reference.

Yes, you are right.

_narrow closes in the object on one particular interface of the current
idl, right? 

What if it is, as in my case, only one interface defined in the idl
altogether?  Should it really be required then?

Another interesting restriction is that the argument to _narrow need to
be a constant, thus I had to change the module name in my idl from
lowercase to uppercase, and consequently also in the Perl code for the
server object. (That it was lowercase in the first place was because it
was so in the original Perl-ORBit example I found on the web and which
I still am deriving new examples from.)

Last, but not least, I do not like using methods (or functions) 
beginning with an underscore as they, to me, indicate that it is a
hidden or internal method that I really should not know about. It is 
the same thing with Perl's CORBA::ORBit _get_the_POAManager method. 
Does anybody else feel the same? Or is it just me that have failed to
appreciate some small but important difference between the
namingconventions of Ruby/Perl and C? ;-)

Best Regards /Selander