Debian Codegraph @

TODO

raw
1 # Implement/Check scalar ties
2
3 # Ensure new is available & documented for V2
4
5 # Check tie behaviour with persistent files (e.g., picks up written values on
6 # first read). 'Component exists' (as opposed to element exists) should be
7 # mean 'tied'
8
9 # Arrays - clear should not delete storage; reset sohuld
10 # Arrays/General - tie should be invoked only upon assignment to the collection
11
12 # Add to list methods:
13 # Add x_clear to reset array without resetting storage (so storage exists, but no members)
14 # x_count(1) - count set values; (2) - count defined values; (3) - count true values
15 # x_grep x_map x_for
16 # x_areset to return a list of indices of set items
17 # ITERATOR
18 # ITERATOR over set values (leave the user to do ITERATOR over defined values,
19 # etc.)
20
21 # Add x_setref to hash, array as discussed in respective 'x' method
22 # documentation.
23
24 # Remaining array tests
25
26 # Integrate Class::MethodMaker::Util
27
28 # Add _exists, _delete(as for hash) to array
29
30 # test forward methods on tied attributes (they're set up in scalar.t,
31 # array.t, hash.t?, just not actually tested)
32
33 # Add introspection
34 # Split doc. for scalar across actual methods, a la array
35 # Tidy up doc writing to eliminiate unnecessary =pod =cut sequences
36
37 # differ clear & reset; define behaviour in terms of storage (therefore, tie)
38 # finish & document array
39 # finish array.t (check test notes at end)
40 # tie scalars
41 # split methods into files in their own directory
42 # split methodmaker further; turn V1 opts into own class hierarchy?
43 # ; remove bits that are needed only for class
44 # manufacture (OPTEXT, more?)
45
46 # document 'new'
47
48 # Check user-defined components still work as they used to
49
50 # Filehandle, Dirhandle, Code components?
51
52 # Automatic storage translation? Retrieval translation? Should this just be
53 # considered a likely implementation of tie? Or implemented with tie? Or
54 # would it be faster directly? This could also be used to implement tied data
55 # _items_, as opposed to tied _components_.
56
57 # Copy method (deep copy? shallow copy? probably an option for both)
58 # freeze/thaw integration (is there really any value in doing this ---
59 # storable already does it)?
60 # Use of array-based classes?
61 # Use of closures for linked-lists, other data-structures (i.e., the instance
62 # is a subref that's closed over the data).
63 # Use of closures as above for iterators?
64 # Iterators over components
65 # Destructor that unties any components
66
67 # Finish Documentation
68 # Reassign names so error messages come from "right" class name & method
69 # Place doc. for data structures in middle of man page
70 # Add +*_clear syntax to add in non-default methods
71 # Add nonnull option
72 # Add triggered & monitored types
73 # Add ints, strings, timedates
74 # Add enums
75 # Document default_ctor simple value trick with -type to work only with class
76 # types.
77 # TODO from C::MM 1
78 # Add trees, linked lists, non-destructive hashes, fib heaps
79 # Integrate other CPAN data structures?
80 # Mechanism to allow users to define templates of methods they commonly use
81 # Test for error messages when new, catalalogue are given "standard" options
82 # Add forwarding from one method to another with a different name. Add
83 # mechanism for auto_naming, e.g., '*_name', where * is replaced by component
84 # name, to allow methods to be forwarded to multiple components e.g.,
85 # { -forward => {mode => '*_mode'} }, qw/ st1 st2 / to allow st1_mode &
86 # st2_mode
87 # What to do with forwarding to a null value --- explicit check?
88 # Require default value? Just let it happen?
89 # Add writing out of source code to generated classes
90 # Add default_count mechanism to array
91 # Add parameter passed to default_ctor of array specifying slot ID
92 # Add purely generated arrays/hashes; unable to set, both with & without a
93 # finite limit. Are there CPAN modules for this?
94 # Add _lock & _unlock methods to lock values. Limit each to certain classes?
95 # Add ties
96
97 # Add introspection capability for OODoc. See email from Marcel Gruenauer
98 # <[email protected]>