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.
Eric On Wed, Sep 8, 2010 at 5:00 PM, Eric Merritt <[email protected]> wrote: > Hmmm, no I don't though I suspect that may have a documentation bug. > If it does portius wont move it over. > > On Wed, Sep 8, 2010 at 4:55 PM, Samuel <[email protected]> wrote: >> Sent. >> >> BTW, do you know what happened to the crary update I tried to upload, >> erlware's repo contains the old 0.2.3 version yet (I uploaded 0.2.5). >> That is holding sinan from upgrading 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.
