| Type | Wish | Status | tested | Date | 20-Oct-2010 11:25 |
|---|---|---|---|---|---|
| Version | alpha 108 | Category | Mezzanine | Submitted by | BrianH |
| Platform | All | Severity | minor | Priority | high |
| Summary | IMPORT into user context by default, unless /no-user |
|---|---|
| Description |
IMPORT currently makes no assumptions about where you want to import stuff, and so isn't quite as practical for script users as one might hope. By default, it only imports into the runtime library. Only the processor of the Needs header does the actual direct importing to the user context. It would be better for IMPORT to do the standard imports into the system and user contexts by default. The existing /only option would prevent all importing. A new /no-user option would just prevent importing to the user context; /only would imply also /no-user. The code that handles the exports to the user context would be moved from the Needs processor to IMPORT itself. |
| Example code |
>> import module [] [t: 1] t == 1 |
| Assigned to | n/a | Fixed in | alpha 110 | Last Update | 2-Nov-2010 06:50 |
|---|
| Date | User | Field | Action | Change |
|---|---|---|---|---|
| 2-Nov-2010 06:50 | BrianH | Status | Modified | built => tested |
| 1-Nov-2010 19:44 | BrianH | Fixedin | Modified | alpha 109 => alpha 110 |
| 21-Oct-2010 01:56 | carl | Fixedin | Modified | => alpha 109 |
| 21-Oct-2010 01:56 | carl | Status | Modified | pending => built |
| 20-Oct-2010 16:46 | BrianH | Description | Modified | - |
| 20-Oct-2010 16:46 | BrianH | Code | Modified | - |
| 20-Oct-2010 16:46 | BrianH | Status | Modified | submitted => pending |
| 20-Oct-2010 11:25 | BrianH | Ticket | Added | - |