Re: Skill-C interface

Keith,

Nice to hear from you!

I must admit after writing that, I had second thoughts, and I'd agree the ITK
API is  a bit tricky. The main problem is really with the documentation, or lack
of it. It always looks like you're seeing just part of the story - again
probably because there aren't that many customers who use it, and it's never got
the attention it deserved.

OA was designed to be public and open from day one, and also having a C++
object model simplifies writing code - it's much more regular.

So I take back my second point, but I'll certainly stick with the first point -
compatibility. That's why the SKILL API has also remained - compatibility was
absolutely key for migration because of the enormous amount of SKILL code
out there (far, far more than ITK).

Andrew.

P.S. Liked Rob Baker's video on www.cadence.com ;-)

On Wed, 26 Nov 2003 09:26:05 +0000, Keith Sabine <[EMAIL PROTECTED]> wrote:

>Andrew Beckett wrote:
>
>> 2. Simplicity - the CDBA interface is probably simpler than the OA interface.
>
>Well it's over 10 years since I did ITK training so my memory
>of the CDBA API is a bit vague, but I'd say OpenAccess
>is a hell of a lot simpler and cleaner. OA has a well structured
>C++ interface and is generally well thought out. And being
>open source it compiles on most things, even Windows :)
>
>- Keith

--
Andrew Beckett
Senior Technical Leader
Custom IC Solutions
Cadence Design Systems Ltd