| Ticket UUID: | 460230 | |||
| Title: | there should be an 'exists -key xyz' | |||
| Type: | Bug | Version: | None | |
| Submitter: | davidw | Created on: | 2001-09-10 11:11:18 | |
| Subsystem: | struct | Assigned To: | andreas_kupries | |
| Priority: | 5 Medium | Severity: | ||
| Status: | Closed | Last Modified: | 2001-09-15 01:14:55 | |
| Resolution: | None | Closed By: | andreas_kupries | |
| Closed on: | 2001-09-14 18:14:55 | |||
| Description: |
There is no way to tell whether a node's key exists or not. If you try and get it and it doesn't exist, it fails with an error. There ought to be a command that you can use to see if it exists or not. | |||
| User Comments: |
andreas_kupries added on 2001-09-15 01:14:36:
File Added - 10793: 460230.diff Logged In: YES user_id=75003 Ok, I created a new submethod 'keyexists' for tree nodes, graph nodes and graph arcs. Attached the patch implementing them, their documentation and additional testcases. davidw added on 2001-09-14 15:14:28: Logged In: YES
user_id=240
Yes, how about:
graphName arc get arc ?-exists key?
or -keyexists or something of that ilk. I think 'get' is a
reasonable place to put these subcommands.
andreas_kupries added on 2001-09-14 07:00:45: Logged In: YES user_id=75003 Note that the 'exists' method is currently used to check the existence of nodes (tree, graph) and arcs (graph). We have to find a different name. andreas_kupries added on 2001-09-12 04:35:56: Logged In: YES user_id=75003 I guess that this applies to graph and tree, but not the others (queue, stack), right ? | |||
Attachments:
- 460230.diff [download] added by andreas_kupries on 2001-09-15 01:14:36. [details]