Virtue SKILL and Python Library

I've not seen that, and I just experimented with using the code above, even putting it inside a function so that the effects of lazy compilation might show up, and putting additional code beyond the macro call, with breakpoints on those lines and all worked fine.

Macros should be used sparingly because you're effectively creating a new language when you use them and that can be jarring for a reader of the code, but this seems a pretty good application for macros. You could write a function instead and use run-time evaluation - which in this case since it's only going to be at load time wouldn't be too awful - but it's much less elegant (and I see no good reason given that the macro works fine with the IDE). I'm not aware of issues with the IDE with macros - maybe they have been resolved?

(defun PkgExportFunc (env @rest functions)
  (let ((pkgTable (makeTable 'pkgTable nil)))
    (foreach func functions
	     (setarray pkgTable func (symeval func env)))
    pkgTable))

and then use:

(PkgExportFunc (theEnvironment) 'set 'get)

to do the export.

Andrew

Curtis,

On reflection (and I’ve. It tried this), the one place I can imagine the IDE might struggle with is putting  break points on code within the arguments of a macro because it doesn’t know which line that ends up on. Possibly… I’d have to check. Obviously that’s not going to be something you’d want to do with the macro I suggested as the arguments are symbols and not code.

So i don’t see this as a reason to avoid all macros.

Andrew

Awesome! That looks great, thanks Andrew Beckett!

I do but I cannot use my personal account at work and even if I enjoy coding in SKILL I don't usually do it on my personal computer which has no access to Virtuoso

All:
I released a new version, v0.4, of Virtue recently.

Documentation:https://www.cascode-labs.org/virtue

Release Notes: https://www.cascode-labs.org/virtue/overview/release_notes.html

-Curtis

Andrew Beckett, AurelBuche