Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Branch: master
Commits on Feb 4, 2011
  1. @JimRoepcke
Commits on Sep 10, 2010
  1. @JimRoepcke
Commits on Sep 2, 2010
  1. @JimRoepcke
Commits on Sep 1, 2010
  1. @JimRoepcke
  2. @JimRoepcke
  3. @JimRoepcke

    add .gitignore file

    JimRoepcke authored
  4. @JimRoepcke
  5. @JimRoepcke

    use llvm 1.5 compiler

    JimRoepcke authored
  6. @mike-anderson @JimRoepcke
Commits on Aug 27, 2010
  1. @kballard

    Add column number to errors

    kballard authored
Commits on Aug 7, 2010
  1. @kballard

    Don't abort on invalid pubDates (fixes #11)

    kballard authored
    If we have an invalid pubDate, just ignore it. This isn't worth aborting
    the parsing over. In this event, just set pubDate to nil.
  2. @kballard
Commits on Jun 28, 2010
  1. @kballard

    Convert README to markdown

    kballard authored
  2. @kballard
  3. @kballard
  4. @kballard
Commits on Jun 24, 2010
  1. @kballard
Commits on Apr 28, 2010
  1. @kballard

    Squelch NSXMLParserDelegate warnings when building for 10.6 (fixes #9)

    kballard authored
    Declare the FPXMLParserProtocol protocol to conform to NSXMLParserDelegate
    when compiling with the MacOSX10.6 SDK. This prevents spurious warnings
    about objects not conforming to NSXMLParserDelegate.
  2. @kballard

    Support odd date format used by Google News (fixes #8)

    kballard authored
    Google News has a weird quirk with its RSS dates where it gives
    every date both a textual timezone as well as a numeric one.
    In addition, it adds a separator between the hours and minutes
    in the numeric timezone. Neither of these quirks are RFC822-compliant.
    We should support them anyway.
  3. @kballard

    Improve error reporting slightly

    kballard authored
    Always display line number where error occurred.
    Display proper error for unparseable <pubDate>
  4. @kballard

    Fix potential crash when aborting

    kballard authored
    When we abort parsing the feed due to an error, we were
    releasing the feed object while it was still possibly
    in the middle of handling something. Ensure that each
    FPXMLParser stays alive at least long enough to finish
    any processing it was doing.
Commits on Mar 24, 2010
  1. @kballard

    Correctly handle the case of text extension elements with no content …

    kballard authored
    …(fixes #7)
    
    When a known extension element with a textual content, such as <dc:creator>, is
    encountered with no actual content, as in <dc:creator></dc:creator>, we must do
    2 things. We must return after aborting parsing when the number of child nodes
    is unexpected, and we must also handle zero child nodes.
Commits on Jan 18, 2010
  1. @jabley @kballard

    Handle dates that are almost RFC822 format, but haven't specified a t…

    jabley authored kballard committed
    …imezone.
Commits on Jan 11, 2010
  1. @kballard

    Restore backwards compatibility for extension elements

    kballard authored
    Ensure all non-RSS/Atom elements always have extension element nodes even when
    these elements are supported directly (such as <content:encoded>). This preserves
    backwards-compatibility in old clients when direct support is added for
    various extension elements. This fixes the tests that were broken by the
    previous commit.
  2. @kballard

    Implement support for <content:encoded> (fixes #4)

    kballard authored
    Implement a new property FPItem.description. This takes the place of the old
    FPItem.content. FPItem.content is now used for <content:encoded>. If the item
    does not contain a <content:encoded> tag, this property will contain the value
    of item.description. This is a mildly backwards-incompatible change, in that
    if a client of FeedParser was using FPItem.content along with the extension
    element mechanism to extract both <description> and <content:encoded>, that
    code will no longer work correctly.
    
    The explicit handling of <content:encoded> removes it from the extension
    element mechanism. A solution to this is forthcoming. In the meantime,
    some tests are expected to fail.
  3. @kballard

    Fix the Content Namespace URI

    kballard authored
Commits on Dec 29, 2009
  1. @kballard

    Correctly handle RFC822 dates with +/-HHMM time zones (fixes #3)

    kballard authored
    RFC822 dates with +/-HHMM dates were not being properly handled.
    The HHMM string was being treated as HHHH and a nil date was being
    returned. A few tests were added to test this functionality,
    and a fix was implemented (thanks jablair).
Commits on Nov 21, 2009
  1. @kballard
Commits on Oct 26, 2009
  1. @kballard
Commits on Sep 15, 2009
  1. @kballard

    Fix a typo (extend -> extent)

    kballard authored
Commits on Apr 12, 2009
  1. @kballard
  2. @kballard

    Add MIT license to the project

    kballard authored
    Add LICENSE.txt file.
    Add MIT license text to the header of every source file.
Commits on Apr 11, 2009
  1. @kballard

    Delete the Demo target

    kballard authored
    The Demo target was really just intended to attach gdb, because OCUnit
    doesn't seem to have a way to do that. However, it is useless as a real demo.
  2. @kballard

    Add README.txt

    kballard authored
  3. @kballard
Something went wrong with that request. Please try again.