Hi,
a remark to this:
the listing output of SPASM could be used by PSIM, but the listing output
of CVASM not. I guess it depends on the listing header. Do intend
TechTools to further develop also PSIM?

I think Andy's offer is nice. I'd say the problem is more simple than it
seems to be. It is not a huge task to write e. g. an AWK script which
convert the new format (or whichever) listing to that required by TDE. I
did a lot of this kind of stuff.
Imre


On Fri, 14 May 1999, Jerry Merrill wrote:

> >
> >A long time ago I volunteered to add macros and conditionals to CVASM for
> >free, and nobody ever got back to me.  The offer still stands.
> >
> >Andy
> >
> >
> >==================================================================
> >   Montana Design Tech Support - http://www.montanadesign.com
> >==================================================================
>
> I appreciate your offer but I would have some reservations.  I would be
> concerned about ripple effects.
>
> TDE derives its debugging information from the LIST file generated by
> CVASM.  Macros would affect the list file and thereby affect TDE's ability
> to parse the file.
>
> Any CVASM changes that affect its list file would have to be designed to
> avoid breaking TDE or would have to be released in conjunction with a TDE
> update, unless that change included generating a COD file as well.  I
> expect generating a COD file is more work than adding the MACROs and
> conditionals.
>
> My point is that updating CVASM itself is only one part of a larger effort.
> There truly is no free lunch.  I expect Parallax was thinking similar
> things when you made them this offer.
>
>
>
>
> Jerry Merrill
>
> jerrym@tech-tools.com
> http://www.tech-tools.com
> FAX: (972) 494-5814
> VOICE:(972) 272-9392
> TechTools
> PO Box 462101
> Garland,  TX  75046-2101
>
>