Fault
view release on metacpan or search on metacpan
=================
Fault::Logger
* FAULT: add an arg_check_isglob to Fault::Logger, or at least some
check that can identify whether a ref is or is not a valid file
handle.
[DMA20080728-?]
* needed in NotePad class
[DMA20080728-?]
* I may not be sufficiently cleansing filename and some other input
strings. I need to do a security audit.
[DMA20080506-?]
* The Msg object is collecting error information I am not yet
logging anywhere.
[DMA20080507-?]
* Since I am now saving the previous Msg object, I can in theory
retrieve pretty much everything about the last fault/log call.
I would have to extend the user API, either more methods here
or one method to return the message object and then suggest
'releasing' that API to the wild instead of keeping it internal
and changeable.
[DMA20080507-?]
* I may want to split much of the general perldoc documentation
out of here and into a dummy Fault.pm package.
[DMA20080508-?]
=================
Fault::Notepad
* fprint needs a fault check for a glob argument.
[DMA20080723-?]
* could add accept either Msg object or a string?
[DMA20080723-?]
* Perhaps allow indexed access.
[DMA20080723-?]
* Objects are intentionally unclearable and uneraseable. Write
a Fault::Notepad::Erasable subclass.
[DMA20080723-?]
* Perhaps add an iterator.
[DMA20080724-?]
=================
Fault::Msg
* FAULT: see if any of the errors I have noted for MAPDigital are in
Faults and if so fix and update it.
[DMA20080728-?]
* FAULT: how could I generate a null message through Msg->new?
[DMA20080728-?]
* I do not yet have any way to dump the list of errors.
[DMA20080723-?]
* Impliment digital signature code.
[DMA20080723-?]
* One might even chain the signatures so that any change of
any prior line invalidates the entire chain of data after
it.
[DMA20080723-?]
=================
Fault::Delegate::DB
* Can I do more checking on the execute calls?
[DMA20080418-?]
* The host argument is not used. Dbh does not support
multiple or non-local db's.
[DMA20080418-?]
* I need to exercise this code under the multiprocessing config
again to make sure none of the changes caused a problem.
[DMA20080418-?]
* There is probably no point in preparing the statement handles
as I cannot use the efficiencies of reusing them due to the
multiprocessing problem. I have left it this way because in the
( run in 1.085 second using v1.01-cache-2.11-cpan-71847e10f99 )