It is a bug, actually -- It's actually logged already under a slightly
different form, but I don't consider the "settable" flag on an API
file when bindings validate. Honestly only one person has ever
pointed this out other than you, so it hasn't been a particularly high
priority. I think most people just end up generating both the getter
and setter, so they never notice? I actually was checking the inverse
case when I started working on this particular bug (make sure you have
the set) -- and hadn't considered that you might just not even define
the "get".
ms
On Mar 21, 2008, at 6:09 PM, Art Isbell wrote:
> Eclipse 3.2.2
> WOLips 3.3.4906
> OS X 10.5.2
> WO 5.3.3
> No WOnder
>
> Certain keys of some WODynamicElements are read-only from the
> WODynamicElement's perspective and thus setter methods aren't needed
> in the WOComponent class (e.g., WOString's "value"). I think that
> certain other WODynamicElement keys are write-only and thus don't
> need getter methods (e.g., WORepetition's "index"). WOBuilder
> didn't flag an error when a WOComponent class didn't implement a
> WORepetition "index" getter as does WOLips.
>
> Are there cases in which a WORepetition needs to read the "index"
> from the WOComponent class? I assume that the index always starts
> at 0. Is it a bug for WOLips to consider no getter method for a
> WORepetition "index" to be an error?
>
> Aloha,
> Art
>
This archive was generated by hypermail 2.0.0 : Fri Mar 21 2008 - 18:16:56 EDT