| Type | Note | Status | tested | Date | 21-Oct-2010 02:10 |
|---|---|---|---|---|---|
| Version | alpha 109 | Category | Unspecified | Submitted by | Carl |
| Platform | All | Severity | minor | Priority | normal |
| Summary | Use TRANSCODE/next not LOAD/next |
|---|---|
| Description |
LOAD is a mezzanine in R3, and it is a significant function! Note it has sub-functions too in order to manage complexity. Normally, if you are using LOAD/next, you want optimal speed. Therefore, you should not be using LOAD at all. You should be using TRANSCODE. What's the difference in speed? In the example below it's 2438% faster. That's why LOAD/next has been removed from R3. Use TRANSCODE. |
| Example code |
b: to binary! "test" >> a: dt [loop 100'000 [load b]] == 0:00:04.396953 >> t: dt [loop 100'000 [transcode b]] == 0:00:00.180318 >> to percent! (a / t) == 2438.4437493761% |
| Assigned to | n/a | Fixed in | alpha 109 | Last Update | 24-Dec-2012 23:23 |
|---|
| Date | User | Field | Action | Change |
|---|---|---|---|---|
| 24-Dec-2012 23:23 | BrianH | Comment : 0003309 | Added | - |
| 21-Oct-2010 06:36 | BrianH | Status | Modified | built => tested |
| 21-Oct-2010 02:16 | carl | Summary | Modified | Concerning LOAD/next vs TRANSCODE/next => Use TRANSCODE/next not LOAD/next |
| 21-Oct-2010 02:16 | carl | Description | Modified | - |
| 21-Oct-2010 02:14 | carl | Description | Modified | - |
| 21-Oct-2010 02:14 | carl | Description | Modified | - |
| 21-Oct-2010 02:13 | carl | Description | Modified | - |
| 21-Oct-2010 02:13 | carl | Status | Modified | waiting => built |
| 21-Oct-2010 02:11 | carl | Fixedin | Modified | => alpha 109 |
| 21-Oct-2010 02:11 | carl | Description | Modified | - |
| 21-Oct-2010 02:11 | carl | Code | Modified | - |
| 21-Oct-2010 02:11 | carl | Status | Modified | submitted => waiting |
| 21-Oct-2010 02:10 | carl | Ticket | Added | - |