From: Hiroo H. <hir...@co...> - 2004-10-21 05:08:08
|
Hi Torsten, > The only reason I found is a "cosmetical" reason. This is the only reason I also think of. (And it is good reason.) > To answer your question I propose to hold the method just for this > reason. And I think it doesn't hurt to hold the "delete" method. > But as you already mentioned this isn't a forcible reason. An user, > who want to "clean" a bank patch, can copy a default patch to the > bank to overwrite an unwanted patch. I think it is more consistent for IBankPatch.delete(int) to put a single patch which createPatch() method of the bank driver uses. BankPatch.createPatch() is an abstract method. core code cannot not know what single patch is filled in by createPatch(). What we can do is to document on IBankPatch.delete(int) method. > I hope my intention about this topic gets clearer to you. Absolutely. Thanks! -- Hiroo Hayashi |