I wish...

1. to never think about encoding again
2. default namespaces would Do What I Mean
3. for a DBD::XML::File, or somesuch, that works a little like DBD::CSV. Specify a directory for the database, a file (or files) for the table and treat XQL and XPath like SQL statements.
4. for a DBD::XML::URI, or somesuch, that works a little like DBD::XML::File but has a nifty URI mechanism.

   --Solo

   --
   Who's scruffy lookin'?

   ---

   In reply to Re: is XML too hard? by Solo
   in thread is XML too hard? by thraxil

   Title:
   Use:  <p> text here (a paragraph) </p>
   and:  <code> code here </code>
   to format your post; it's "PerlMonks-approved HTML":
   
   
   
   

   ---

   • Are you posting in the right place? Check out Where do I post X? to know for sure.
   • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

     <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

   • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
   • Want more info? How to link or How to display code and escape characters are good places to start.