On 4 Apr 2000, Thomas Mittelstaedt wrote:
> > LibXMI is now available via public CVS, with both anonymous
> > read-only and account-based read/write capability. Point your CVSROOT
> > thusly:
>
> I grabbed the latest snapshot of your libxmi effort and integrated it into a bigger
> app.
>
> I observed the following:
>
> i) Not initializing libxmi via xmiInit and xmiAttach causes seg fault as soon as
> one tries to use an mi.. function. Error checking??
Lacking in many places in the current version.
> ii) miFillPolygon causes segmentation violation, replacing with miDrawLines worked
There's broken pointers all over the code.
> iii) >>> miDrawArcs === x: 4, y: 440, w: 400, h: 18, arc1: 90, arc2: 90
> libxmi: out of memory: Cannot allocate memory
>
> Use of miFillArcs, instead, leads to segmentation violation again.
>
> I could start the demo.c sample program without problems, though.
demo.c is the code I used to test against, so it is not
surprising.
> I conclude, that libxmi is not ready for serious work yet. True??
Yes. It is close, but as you have seen there remains some tidying
up to be done.
Jon
---
'Cloning and the reprogramming of DNA is the first serious step in
becoming one with God.'
- Scientist G. Richard Seed
