| Type | Wish | Status | dismissed | Date | 4-Aug-2009 23:45 |
|---|---|---|---|---|---|
| Version | alpha 76 | Category | Mezzanine | Submitted by | BrianH |
| Platform | All | Severity | minor | Priority | normal |
| Summary | IMPORT /into context option |
|---|---|
| Description |
This is basically a similar option to #1180 for DO-NEEDS, but for IMPORT instead. If you IMPORT /into block!, then the block would be bound to the module instead of the module doing the standard import process. If you IMPORT /into object!, then the object! would be resolved from the words of the module. In both cases, all of the module's local words would be applied, not just the exports - the /into option is just a shortcut for two of the most common usage patterns of IMPORT/only. The /into option would imply /only - the standard import process would be skipped. IMPORT block /into context would just pass the /into option along to DO-NEEDS (see #1180). This would be a 3-line fix to IMPORT, plus the added parameters in the function spec. |
| Example code |
| Assigned to | n/a | Fixed in | - | Last Update | 21-Aug-2009 07:15 |
|---|
| Comments | |
|---|---|
|
(0001538)
BrianH 21-Aug-2009 07:15 |
Since #1186 was dismissed,, #1180 had to be dismissed too, and without that there is no point to complicating IMPORT any further.
Use /only and then BIND or RESOLVE the returned module as you see fit. |
| Date | User | Field | Action | Change |
|---|---|---|---|---|
| 21-Aug-2009 07:15 | BrianH | Comment : 0001538 | Added | - |
| 21-Aug-2009 07:12 | BrianH | Status | Modified | pending => dismissed |
| 5-Aug-2009 00:20 | BrianH | Description | Modified | - |
| 5-Aug-2009 00:20 | BrianH | Status | Modified | submitted => pending |
| 4-Aug-2009 23:45 | BrianH | Ticket | Added | - |