<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>xpcom on Oxymoronical</title>
    <link>https://www.oxymoronical.com/blog/tag/xpcom/</link>
    <description>Recent content in xpcom on Oxymoronical</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 14 Jun 2010 23:45:50 +0000</lastBuildDate>
    <atom:link href="https://www.oxymoronical.com/blog/tag/xpcom/feed/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Multiple breaking changes are coming for components in extensions</title>
      <link>https://www.oxymoronical.com/blog/2010/06/Multiple-breaking-changes-are-coming-for-components-in-extensions/</link>
      <pubDate>Mon, 14 Jun 2010 23:45:50 +0000</pubDate>
      <guid>https://www.oxymoronical.com/blog/2010/06/Multiple-breaking-changes-are-coming-for-components-in-extensions/</guid>
      <description>&lt;p&gt;Are you an extension or application developer? Have you written any XPCOM components, JS, binary or otherwise? If not you can probably ignore the rest of this post, unless you are interested anyway.&lt;/p&gt;&#xA;&lt;p&gt;If you do then you might be interested to hear that your components are probably going to break in an upcoming Firefox nightly, maybe as early as next week. I’m going to blog specific examples on the changes you need to make once we have better documentation up and builds to test against, for now it is just important for you to know that the changes are coming.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
