| Ticket UUID: | 1616470 | |||
| Title: | Generate errorCode data | |||
| Type: | Patch | Version: | None | |
| Submitter: | dkf | Created on: | 2006-12-15 15:19:33 | |
| Subsystem: | 45. Parsing and Eval | Assigned To: | dkf | |
| Priority: | 5 Medium | Severity: | ||
| Status: | Closed | Last Modified: | 2008-01-17 06:35:07 | |
| Resolution: | Out of Date | Closed By: | dkf | |
| Closed on: | 2008-01-16 23:35:07 | |||
| Description: |
Attached patch makes a number of places in the core (especially those that look things up by name) generate ::errorCode information when they fail. | |||
| User Comments: |
kennykb added on 2007-04-20 11:58:01:
Logged In: YES user_id=99768 Originator: NO Hmmm, we need to document what ::errorCodes are generated - the existing ones are in tclvars.n. Aside from that, this looks like quite a nice idea. Might it still be possible to get it into 8.5, with the help of $env(LC_DEITY) and a shoehorn? Could you *please* not do whitespace policing at the same time as you're cutting a patch to share with others? It makes applying the patch quite a challenge, and even reading it is rather confused by the irrelevant changes. dkf added on 2006-12-15 22:19:34: File Added - 207374: errorcode.patch | |||
Attachments:
- errorcode.patch [download] added by dkf on 2006-12-15 22:19:33. [details]