Re: Consensus on getter conventions?



> 
> 	First, I don't really see this as a huge problem.  Putting results
> into variables (instead of using nested function calls) makes for more
> readable code.  But you do have a point...
> 
> 	Second, apparantly Karl's method causes problems for other
> languages (at least, it does for Java).

I didn't read the java message that way.  He said he need the number
of in/out arguments capped at one.  C++ needs the same for most 
functions.  More than one means ugly C++ interface. 

Note, that gtk+ constantly has more than 1 in/out parameter in
many functions that cause bindings problems.

--Karl








[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]