We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What do you think about redefining the macro from this:
(defflavor <flavor-name> (<var1> <var2> ...) (<flav1> <flav2> ...) <opt1> <opt2> ...) (defmethod (<operation>) <lambda-list> <form1> <form2>) (defmethod (<operation> <method-type>) <lambda-list> <form1> <form2>) (endflavor <flavor-name>) ;Must be last after the methods
To this?
(defflavor <flavor-name> (<var1> <var2> ...) (<flav1> <flav2> ...) (<opt1> <opt2> ...) (defmethod (<operation>) <lambda-list> <form1> <form2>) (defmethod (<operation> <method-type>) <lambda-list> <form1> <form2>) ...)
Thus obviating the need for the endflavor ...
endflavor
Maybe we could keep the old one for backwards compatibility, and name the new one deflavor? (one 'f' instead of two 😉)
deflavor
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What do you think about redefining the macro from this:
To this?
Thus obviating the need for the
endflavor
...Maybe we could keep the old one for backwards compatibility, and name the new one
deflavor
? (one 'f' instead of two 😉)The text was updated successfully, but these errors were encountered: