Re: gEDA: Re: "FREE" CPLD fitter tools

[Stephen Williams <steve-at-NOSPAMicarus_dot_com>]

graham@belegost.mit.edu said:
>  Using this scheme, say I want to have nested objects. For example,
> jedec_data contains a cookie of architecture_data_t, which is a
> pointer to architecture_data which in turn contains a cookie of
> fuse_array_t, pointing to a fuse_array. Am I right to think the
> preprocessor can't handle this?

You mean the compiler can't handle this, and yes, you need to write
accessor functions. Look at the ivl_target.h header file from the
Icarus Verilog source for a fairly complete and involved example of
this sort of style.

Also take a look at the latest pld.tgz for an idea how I made it work
in the case of JEDEC. In your case, you may be adding more indirection
then is really needed, and as a consequence making the interface more
complex then it needs to be.

    <ftp://icarus.com/pub/eda/pld.tgz>

Specifically, I doubt the need for a fuse_array_t. I also doubt the
need to associate the architecture data type with a jedec file. The
JEDEC data is just an unstructured list of fuses. For example, I'm going
to want to get the architecture of a 22v10, but I shouldn't need to
read a jedec file to get it.
-- 
Steve Williams                "The woods are lovely, dark and deep.
steve@icarus.com              But I have promises to keep,
steve@picturel.com            and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."