Opened 11 years ago
Closed 4 years ago
#3273 closed defect (fixed)
Basic type Clock conflicts with other classes and components with the same name
| Reported by: | Adrian Pop | Owned by: | Adrian Pop |
|---|---|---|---|
| Priority: | high | Milestone: | 1.19.0 |
| Component: | New Instantiation | Version: | trunk |
| Keywords: | Cc: | Bernhard Thiele |
Description
Until m:#1538 is decided I think we should be able to handle such name clashes in the compiler by checking that the environment of the basic type Clock is top.
Change History (2)
comment:1 by , 11 years ago
| Cc: | added |
|---|---|
| Owner: | changed from to |
| Status: | new → accepted |
comment:2 by , 4 years ago
| Component: | Frontend → New Instantiation |
|---|---|
| Milestone: | Future → 1.19.0 |
| Resolution: | → fixed |
| Status: | accepted → closed |
Note:
See TracTickets
for help on using tickets.
This was fixed in the new frontend in cd88b9e8, since it's been decided that
Clockshould not be a reserved name. So we not just treat it as a top-level type instead.