Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate checking the API from printing the statuses #4

Merged
merged 2 commits into from
May 8, 2016
Merged

Separate checking the API from printing the statuses #4

merged 2 commits into from
May 8, 2016

Conversation

Feufochmar
Copy link

In order to make the issue #2 easier to deal with, I have separated the API checking from the status printing. A result table is firstly constructed and contains the type of element checked (module, function, type), its name, status (ok, missing, unknown), and the results for its children (the functions in a module for instance).
There are also differences from the previous version:

  • every function is checked, even those in missing modules; they are marked as missing, this should be better for computing the percentage, as asked in issue Add percent complete #1
  • all types are listed but reported with an unknown status, as a starting point for issue Check the methods of types #3

end

lib.update = function (dt)
-- Now that the application has loaded, exit.
lib.window.close()
-- Note: closing the window does not exit love
if (lib.event ~= nil) and (lib.event.quit ~= nil) then
lib.event.quit()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also added lib.event.quit() to Lutro recently too. Should we should be good to switch to that once builds are out.

@RobLoach RobLoach merged commit 984273d into libretro:master May 8, 2016
@RobLoach
Copy link
Member

RobLoach commented May 8, 2016

Looks great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants