Le mardi 26 mai 2020 21:45:21 UTC+2, johnbclements a écrit :
> In your case, the type checker would also be “resolving” lightweight
> expressions like (assign (h1 a) a) into fully-decorated expressions like
> (assign (port-ref half-adder h1 a) (port-ref full-adder a)) .
> Does this make
Le mardi 26 mai 2020 21:41:14 UTC+2, Sam Tobin-Hochstadt a écrit :
> I think the best way to implement what you describe for a "better
> version" is as follows:
> Expand `(instance h1 half-adder-arch)` into something like
> (define-syntax h1 (half-adder-arch-info))
I have seen this
Le mardi 26 mai 2020 03:59:59 UTC+2, johnbclements a écrit :
> > So far, I have made two attempts to work around these issues: (1) by
> creating a metamodel-like data structure using Racket structs, and
> transforming syntax objects into struct instances; or (2) using syntax
> objects only
Thanks for your answer.
Le vendredi 22 mai 2020 13:57:53 UTC+2, Stephen De Gabrielle a écrit :
> What are the Racket Syntax Classes you have implemented? Can you provide
> an example?
The project consists in creating a simple hardware description language.
I am preparing a
further illustrate what I want to do and where I am stuck.
Have you experienced similar concerns in one of your projects?
What design patterns would you recommend ?
Do you know any well-commented real-life example that I could use for
Thanks in advance for your answers.
Mail list logo