-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Trevor and Jenny Williams wrote: | I figured that new VPI enhancements would only be added after your new | development release is finally made. I'm guessing that things like loops | and case statements fall in the realm of uncompiled behavioral source? If | I'm wrong in understanding this, could you correct me? | | I think, when I get going, that I will probably need handles to expressions, | statements, events in addition to what is already provided. It would be | beneficial to (eventually) add things like handles to case statements, for, | while, repeat, force, release and the like. I'll know more when I get | things moving on my end.
Sounds like a plan. Currently, there are no VPI objects for the statements. Actually, you are pointing out a problem there, as the generated instructions do not exactly match the statements of the original source. (The idea is to compile down to a simpler form.) I'll have to look at the meanings of the behavioral code VPI objects to see what it means. A solution to this knot serves another purpose, source line debugging will need some very similar information, so it is a knot worth untangling. I'm *really* close to making the first post-0.8 snapshot. I think I just need to get sequential UDPs working vectorized and repair a few oddball gates and it'll be back to the place in the regression suite where I was before I started digging trenches. - -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFCpwY+rPt1Sc2b3ikRAhy1AKCJxJ4PQmFoKMy1AIRd7iTfOAWsXACdHyoN K0GwcwyIEwrsCn37tsexmTw= =+Gvz -----END PGP SIGNATURE-----
