Opened 4 years ago
Last modified 20 months ago
#459 new defect
Defsetf Lambda-Lists Don't Permit the &environment Parameter
| Reported by: | Mark Evenson | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 1.8.1 |
| Component: | interpreter | Version: | 1.6.0-dev |
| Keywords: | com.github-88 | Cc: | |
| Parent Tickets: |
Description
https://github.com/armedbear/abcl/issues/88
This is in violation to 3.4.7 which specifically allows the &environment parameter in defsetf lambda-lists. Test case: (defsetf foo (&environment env place) (value)) ;; => &ENVIRONMENT is only valid at top level of lambda list. I'm not entirely sure if 3.4.7 requires &environment to come after the places, unlike other lambda-lists where &environment has to be first. In any case, late &environment also fails in the same fashion. (defsetf foo (place &environment env) (value)) ;; => &ENVIRONMENT is only valid at top level of lambda list.
Change History (7)
comment:1 Changed 3 years ago by
| Milestone: | 1.6.0 → 1.6.1 |
|---|
comment:3 Changed 2 years ago by
| Milestone: | 1.6.2 → 1.7.0 |
|---|
comment:7 Changed 20 months ago by
| Milestone: | 1.8.0 → 1.8.1 |
|---|
Ticket retargeted after milestone closed
Note: See
TracTickets for help on using
tickets.
Ticket retargeted after milestone closed