A new begin for Jericho

Jericho was the first Orizon subsystem, even before Twilight.
In the very first Orizon versions you were able to find some kind of input not validated. This is done by Jericho engine, however that code was buggy and it was not compliant to newer Orizon engine based architecture.

That’s why I renamed Jericho class in OldJericho and started rewriting from scratch a new Jericho engine, extending Engine class.

The first task newer Jericho has to accomplish is to check source code for design weakness. In the Orizon library JAR file, there is now a folder called Design/ containing ORL rule files describing what is bad in source file design.

The “scan” command will added in Orizon SHell in order to invoke Jericho asking for static analysis features.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s