or: Static Analysis of nil Values in Ruby Code used in YaST.

YaST is written in Ruby. A large part of the code is Ruby that was transpiled from the YCP language during the YCP Killer project. To preserve behavior in various edge-case situations, mostly when nil was passed around, helper libraries were used. The resulting code is often long and hard to work with.

Example from SlideShow.rb:

total_time = Ops.add( total_time, Ops.divide(Ops.get_integer(stage, "value", 0), 3495) )

The plan is to find patterns in Y2R-generated code which can be safely translated into more native Ruby code and translate them. In many cases this will require proving that the edge cases mentioned above can't happen (e.g. that passed parameters can't be nil). This will be done using static analysis on the code.

We have started this during HackWeek 11 with the Zombie Killer project, but did not finish back then.

Since that time, we started using RuboCop in the team to keep a consistent code style. It is a natural match to bring RuboCop and Zombie Killer together, since both are based on the Parser library. RuboCop-YaST was started by Ladislav Slezak, but Zombie Killer is not fully integrated and working.

During HackWeek 13 the goal is to have a safely working RuboCop-YaST that is able to resocialize some zombies in production code.

Looking for hackers with the skills:

ruby compiler

This project is part of:

Hack Week 13

Activity

  • almost 6 years ago: IGonzalezSosa liked this project.
  • almost 6 years ago: mvidner added keyword "ruby" to this project.
  • almost 6 years ago: mvidner added keyword "compiler" to this project.
  • almost 6 years ago: mvidner started this project.
  • almost 6 years ago: mvidner originated this project.

  • Comments

    Similar Projects

    Dawnscanner: revive the project and create an RPM package by pperego

    [comment]: # (Please use the project descriptio...


    Requirements Management Tool on Graph Database by mknop

    Project Description

    Create a requirements...