Skip to main content

OCaml RSS Feed Parser

Using Cameleon RSS Feed Parser

Looking for a way to parse RSS (or ATOM) feeds with OCaml, I performed a Google search on "ocaml rss":

Here is how to begin to use it...

Installing on Ubuntu/Debian

I assume the user has all de basic OCaml installation. Installing the RSS feed parser requires:

     sudo apt-get install libcameleon-ocaml-dev cameleon    

Getting a sample RSS file

Let's get the RSS2 file of OCamlCore:

     wget http://planet.ocamlcore.org/rss20.xml    
The file is saved as "rss20.xml" use the -O option of wget if you want another saving name.

Using it in the toplevel

The user needs to load several modules:

        Objective Caml version 3.11.2       #use "topfind"                  ;;     #require "unix"                 ;;     #require "cameleon"             ;;     #require "cameleon.config_file" ;;     #require "cameleon.configwin"   ;;     #require "cameleon.ffind"       ;;     #require "cameleon.gdir"        ;;     #require "cameleon.gmylist"     ;;     #require "cameleon.gstuff"      ;;     #require "cameleon.okey"        ;;     #require "cameleon.report"      ;;     #load "/usr/lib/ocaml/cameleon/rss.cma";;    
Load the XML RSS file (Pretty Long output)
     let my_channel = Rss.channel_of_file "rss20.xml";;    
Get the list of items (Pretty Long output)
     let items = my_channel.Rss.ch_items);;    
Grab the first item
     List.hd items;;    
Get the title of that first item
     (List.hd items).Rss.item_title;;    

Note

Please note that it is a quick and dirty way to do it, the reader is encouraged to suggest cleaner ways by commenting this post.

Comments

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo&

dockerfile multiline to file

Outputing a multiline string from Dockerfile I motsly use a Dockerfile by sourcing from a base ditribution: CentOS or Debian. But I also have a local mirror and would like to use it for packages installation. Espacially on CentOS it is about many lines to write to the /etc/yum.repos.d/CentOS-Base.repo file. Easiest way: one RUN per line The first method that comes in mind is to issue one RUN per line to write. Here you are: RUN echo "[base] " > /etc/yum.repos.d/CentOS-Base.repo RUN echo "name=CentOS-$releasever - Base " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "baseurl=ftp://packages-infra.mg.rktmb.org/pub/centos/7/base-reposync-7 " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "gpgcheck=0 &quo

Jira workflow for new projects

Associated workflow creation I'm a Jira Cloud user and begining from some version 6, I noticed that when I create a project, it automatically creates a Workflow and Issue Scheme that is prepended by the project key and which is a copy of the default scheme. I always had to make a cleanup after creating a project. Default workflow for new projects I also miss a feature that would allow me to make a custom workflow (and globally custom project setting) the default for new projects I create. Solution: Create with shared configuration While searching, I noticed that with Jira Cloud which is version 7.1.0 at the time I write, there is a link at the bottom of the "Create project" wizard: "Create with shared configuration" will allow me to select the project I want the new one to share configuration with. The new created project will use the same configuration as the project I select There will be no creation of Workflow and Issue Scheme that