Proof of Concept for a Perl binding to libfyaml
a project by tinita
Updated almost 3 years ago. No love. 1 follower.

Project Description

Similar to YAML::LibYAML::API and YAML::XS it would be nice to have a Perl binding to libfyaml.

libfyaml is a modern alternative to libyaml that passes all current YAML 1.2 tests from the official YAML Test Suite, see the matrix.

Goal for this Hackweek

Goal: be able to run a very basic function using libfyaml's event parsing API with perl XS.

Resources

Join this project

Looking for hackers with the skills:

yaml libyaml perl libfyaml

This project is part of:

Hack Week 22

Activity

  • almost 3 years ago: tinita started this project.
  • almost 3 years ago: tinita added keyword "perl" to this project.
  • almost 3 years ago: tinita added keyword "libfyaml" to this project.
  • almost 3 years ago: tinita added keyword "yaml" to this project.
  • almost 3 years ago: tinita added keyword "libyaml" to this project.
  • almost 3 years ago: tinita originated this project.


    • Comments

    Be the first to comment!

    Similar Projects

    Create a page with all devel:languages:perl packages and their versions by tinita

    Description

    Perl projects now live in git: https://src.opensuse.org/perl

    It would be useful to have an easy way to check which version of which perl module is in devel:languages:perl. Also we have meta overrides and patches for various modules, and it would be good to have them at a central place, so it is easier to lookup, and we can share with other vendors.

    I did some initial data dump here a while ago: https://github.com/perlpunk/cpan-meta

    But I never had the time to automate this.

    I can also use the data to check if there are necessary updates (currently it uses data from download.opensuse.org, so there is some delay and it depends on building).

    Goals

    • Have a script that updates a central repository (e.g. https://src.opensuse.org/perl/_metadata) with metadata by looking at https://src.opensuse.org/perl/_ObsPrj (check if there are any changes from the last run)
    • Create a HTML page with the list of packages (use Javascript and some table library to make it easily searchable)

    Resources