Opened 14 years ago
Last modified 3 years ago
#278 new defect
closer-mop:class-finalized-p returns t without ever running finalize-inheritance method
| Reported by: | ehuelsmann | Owned by: | ehuelsmann |
|---|---|---|---|
| Priority: | blocker | Milestone: | 1.9.3 |
| Component: | (A)MOP | Version: | 1.2.0-dev |
| Keywords: | needs-test | Cc: | |
| Parent Tickets: |
Description
Report by stassats on IRC.
He's drawing up a testcase as we speak.
Change History (21)
comment:1 by , 14 years ago
| Priority: | major → minor |
|---|
comment:2 by , 14 years ago
| Milestone: | 1.1.1 → 1.2.0 |
|---|
comment:3 by , 14 years ago
| Priority: | minor → blocker |
|---|---|
| Version: | → 1.2.0-dev |
comment:4 by , 13 years ago
| Milestone: | 1.2.0 → 1.3.0 |
|---|
comment:7 by , 13 years ago
| Milestone: | 2.0.0 → 1.4.0 |
|---|
comment:13 by , 6 years ago
| Milestone: | 1.6.2 → 1.7.0 |
|---|
comment:18 by , 4 years ago
| Milestone: | 1.8.1 → 1.9.0 |
|---|
comment:19 by , 4 years ago
| Milestone: | 1.9.0 → 1.9.1 |
|---|
comment:20 by , 4 years ago
| Milestone: | 1.9.1 → 1.9.2 |
|---|
comment:21 by , 3 years ago
| Milestone: | 1.9.2 → 1.9.3 |
|---|
Note:
See TracTickets
for help on using tickets.
So, the problem turns out that finalize-inheritance is run just after initialization is complete. And I had finalize-inheritance :after method defined in another file, after the defclass form in question. On other implementations finalize-inheritance is run just before allocate-instance, so such problems don't come up.