Add indentation checks for code inside classes and fix appeared issues.

[sand1k]

Add indentation checks for code inside classes and fix appeared issues.
Fix asserts in test_recordset.cpp.

[egavrin]

Good to me.

[zherczeg]

What is the C++ status in Jerry? Is it allowed?

[sand1k]

@LaszloLango, The reason for using one space is to highlight scope of the class (to easily find its boundaries). To my mind, both ways are alright, so we could stick to any of them.
BTW, in V8 one space indentation is used. Don't you know the motivation?

[LaszloLango]

@sand1k I can live with it. :) We can use one space if I am the only one who doesn't like it.

[sand1k]

@LaszloLango, we discussed this with @egavrin and decided that this indentation is not needed so I'll fix the patch.

[egavrin]

What is the C++ status in Jerry? Is it allowed?

@zherczeg, as we discussed earlier, we should keep existing code "as is"
without introducing C++ features globally, until we all would agree to use C++ in this project.

The reason for using C++ in the following components: rcs_recordset_t
and lit_storage_t - is to boost the development of core functionality.

This code could be written in C, but implementation would be less effective and much more complicated due to manual emulation of inheritance.

So we used inheritance and virtual functions in this particular implementation because it simplifies interfaces in comparison to C, while not affecting performance and code size.

As we discussed on CC, we consider to use some kind of restricted C++ subset for embedded systems in future. We are preparing a proposal which describes features of C++ that could be effectively used without affecting performance, memory consumption and code size comparing to C.
We hope to get your feedback on this subset and collaborate on its development, aiming to use it across Jerry and IoTjs projects.

I request you to approve these changes for now. If we would decide to revert C++ usage globally after future investigation, we will rewrite these parts, for example, this could be done during "optimization stage"
in July and August.

From my point of view, usage of limited C++ subset would allow us to significantly simplify code base and provide more flexibility in development, while enabling C++-specific optimizations.

[sand1k]

@LaszloLango, I updated the pull request according to your notes. Please, check.

[egavrin]

This commit was LGTM'ed by @LaszloLango and me, but comments are missing now, due to rebasing.