| Type | Issue | Status | reviewed | Date | 2-Sep-2009 09:51 |
|---|---|---|---|---|---|
| Version | alpha 81 | Category | Native | Submitted by | pekr |
| Platform | Windows | Severity | minor | Priority | normal |
| Summary | CALL needs more R2 features |
|---|---|
| Description |
In R2, we have quite robust CALL implementation, which enables us to deploy REBOL into foreign environments. You can e.g. use it to get DB connection to MSSQL, SQLite, simply in situations, where no DB driver is available. It is imo essential for R3, to have usable CALL. But R3 got all new implementation, which lefts much to be desired. I have following issues: 1) no call/wait - you REBOL app continues its execution, not waiting for the output 2) no call/output - R3's CALL returns to R3 console, but you can't easily trap the output into variable! You have to use command line output redirection '> to file, reading the file later, or REBOL's 'echo. 3) after CALL returns to REBOL, you need to press enter to continue! If we don't address those issues, then you can be sure that CALL is one of those reasons, why ppl are not using R3 productively yet. |
| Example code |
REBOL [] call "cmd /c dir c:" result: 1 + 1 print result halt ;--- 1) 'result is printed ;--- 2) dir c: output is printed ;--- 3) console hangs, waiting for enter |
| Assigned to | n/a | Fixed in | - | Last Update | 2-Sep-2009 17:55 |
|---|
| Date | User | Field | Action | Change |
|---|---|---|---|---|
| 2-Sep-2009 17:55 | carl | Summary | Modified | CALL almost unusable => CALL needs more R2 features |
| 2-Sep-2009 17:55 | carl | Description | Modified | - |
| 2-Sep-2009 17:55 | carl | Code | Modified | - |
| 2-Sep-2009 17:55 | carl | Status | Modified | submitted => reviewed |
| 2-Sep-2009 09:51 | pekr | Ticket | Added | - |