Re: [PEPr] +1 for File Formats::File_DNS

> >>This vote is conditional. The condition is: > >>It would be nice to have an "$file->isValid()" function. ;) > > As it's set up right now, the code will return a PEAR_Error if you try and > > load a file that's not valid. Is this what you mean? > > Or do you mean an isValid() function to check the changes made by the user? > > To make sure there are no A's pointing at www.example.com, or MX with a > > preference of -14.2 ? I plan to have validation of the data supplied with > > the addRecord/setFoo fuynctions implemented before I declare the package > > even beta :) > actually I mean both. I've tested it with the PEAR::isError() but saw > that $loaded->getUserInfo() or $loaded->getDebugInfo() aren't returning > sufficient info to see where is the error in the file (what line, > column, etc). I think this kind of information is very usefull. > But seeing your roadmap, thats ok. Okay, I'll be sure to double-check all the PEAR_Error's, and see if I can add more information about where and why it failed. All errors should already have a define() linked to them, plus most return the item they couldn't parse. I'll see if I can easily add linenumbers and such to that, to even more easily locate the line and item that are invalid. Cipri