Re: Enhancing StarBasic then ? (Re: [api-dev] use of css.container.EnumerableMap
Frank Schönheit <[email protected]> Wed, 05 Jan 2011 12:48:52 +0100
| Newsgroups | gmane.comp.openoffice.devel.api |
|---|---|
| Message-ID | <[email protected]> |
Hi Andreas, > >> Il 21/12/2010 10:25, Frank Schönheit ha scritto: > >>> as I was the one who wrote this service (out of a particular need): > >>> Sorry, I wasn't aware that Type is such a ... difficult thing in Basic. > >>> I'll keep that in mind for the next API I design :-\ > > This is the wrong way, I think. Handling type correctly clearly is a > problem that has to be solved in Basic. Other problems in other lan- > guage bindings have to be solved there. Otherwise designing new API > would end up in painfully searching a way around all kind of obstac- > les that may be set by different language bindings. Not very nice. :-) Sorry, I wasn't precise here: Of course the root cause should be fixed in Basic's UNO binding (and I like your ideas you sketched in the other mail). What I wanted to say is that I shall pay more attention to how usable an API is in the different bindings. Usually, I only design the API as such, but don't think about pitfalls of the various UNO bindings. If I had, and if I had tried the API in Basic, the bugs in Basic's binding would have been found earlier, and perhaps fixed before release of the new API into the wild. Ciao Frank