hmm, maybe a differente name.'parse' or something similar and cause decode to throw an exception?
On Thu, Sep 9, 2010 at 1:30 AM, Samuel <[email protected]> wrote: >> Ok samuel, I am going to go with edwin and martins suggestion. Lets >> depricate the api, have the old api throw an exception and the new api >> work. That should be easy enough. I can do this or you can at your >> option. > > I was thinking about that also. but since we are changing output > types, the only thing I come up with is creating a new function > ktj_decode:??? and make ktj_decode:decode throw an exception. I can do > that easily, I just need a good name for ??? :D > > Also, I realised that I didn't write a test for the -0.1 bug, I > discovered that through my own test suite, but ktuo tests wouldn't > fail if that bug appears again. I'd add that also. > > Cheers > -- > Samuel > > -- > You received this message because you are subscribed to the Google Groups > "erlware-dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/erlware-dev?hl=en. > > -- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
