Re: RE : [PEAR-DEV] Mod 10 for Payment package?

> > Well, it's a decision - but it's not an "open" decision. If we're > > > > going to change the behaviour we would need to change it for the > > whole Validate - or state that we use it in all specialised classes. > > This or that way we whould have to agree upon something general (for > > Validate, and maybe for other packages too). > > As Bertrand put it: It's against the "keep it simple" [tm] > > Wouldn't it be simpler to just stop all development altogether, and in > fact, just use everything as is? There are plenty of validation > solutions out there. In fact, wouldn't it be simpler to drop PHP > altogether? Other languages do exactly the same thing. > > I guess I'm more of a "do it the best way" [tm] kind of guy. Simple can > only go so far - it's simpler for the programmers of Validate, but is it > really simpler for the users of Validate? If you do want to determine > *why* something is broken, you can't. You must instead do a whole > series of complex programming things to answer a question that could > have been easily answered by the Validate class to begin with. Is that > really simple? You have a point. I've been giving error_raise a shot, it has a steep learning curve, true but it's quite powerful. > It would also be simpler to just live in the woods and kill what you > plan on eating when you want to eat it. However, when you catch a > debilitating disease from what you eat, it would be simpler to have a > hospital around than to try to get better by yourself :). Now you have an idea, living like an elf ;) > Greg > > P.S. it's www.chiaraquartet.net/apidoc - 3 a's in the word for some reason i'm having a hard time remembering that address.