-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
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
Design code inheritance. #133
Comments
bigeasy
pushed a commit
that referenced
this issue
Nov 27, 2020
Pretty much how it is going to work. Symbol is inherited by properties such as message format can change. See #133.
Reopening because we have to inherit both codes and aliases now. |
bigeasy
pushed a commit
that referenced
this issue
Dec 2, 2020
Thinking aloud about inheritance. Do not want to have descendent classes inherit templates by default. Don't really want it to happen at all, but certainly not by default. Looking to create a symbol based system, which is probably something of an abuse, certainly is uninviting, but the alternative is to do nothing and suggest the user defined reusable codes as a code function they share between exceptions. At least there's a mechanism. Who creates error hierarchies in JavaScript anyway? See #140. See #133.
bigeasy
pushed a commit
that referenced
this issue
Dec 3, 2020
Working through code definition and started with updating `create`'s `vargs` processing so that an array can include anything that is an argument and gets unshifted onto the `vargs` so that definitions are recursive. This means code functions can return arrays. Also, there's an ambiguity between an initial code function and the super class. They are both functions. See #140. See #133.
bigeasy
pushed a commit
that referenced
this issue
Dec 5, 2020
All in one place so I can work on it with the documentation. See #133.
bigeasy
pushed a commit
that referenced
this issue
Dec 6, 2020
Not sure why this didn't occur to me earlier. I was using `symbol` as a way to specify a template base, but that shouldn't have blocked the recognition of this modification. See #133.
bigeasy
pushed a commit
that referenced
this issue
Dec 8, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Need to determine how codes are inherited in derived exceptions.
The text was updated successfully, but these errors were encountered: