do you like the 7 rules i use?

[asetof...@gmail.com]

1) not have fear in use goto
in a function
because from goto born all
2) use return address and never
exceptions
because library has not stop
the program
3) in class use some variable that
says if each element of the class
has the right memory and are ok
as they are born
and use this at start of function
for see if every object of class
is ok (after they are born)
4) use some memory allocator that
find leak and memory errors
5) for portability use fixed size
types as u8 u32 u64 only
6) use some big num class for
signed unsigned, fixed float
limited only from memory
where from float one can say
number of digit ok after the
point
7) use only class, overload, template
and code as C and no other.
use ra2 almost always.

[asetof...@gmail.com]

I forget
8) for C like code:
use function for return error
code to the caller

for code use class
can be useful to have one variable
that says that object is or not is
the error object.
(error object is one object
that used for build other object
has as result one error object)

What do you say?

[asetof...@gmail.com]

But where are all? To follow
conferences?

[Öö Tiib]

On Saturday, 24 October 2015 10:45:52 UTC+3, asetof...@gmail.com wrote:
> But where are all? To follow
> conferences?

Sorry, but your seven rules did look uninteresting trolling that was
perhaps inspired by "Bjarne Stroustrup announces C++ Core Guidelines"
thread and nonsense ramblings of Ramine. Such threads deserve silence
as answer.

[Gareth Owen]

Öö Tiib <oot...@hot.ee> writes:

> Such threads deserve silence as answer.

And yet, here you are.

[Öö Tiib]

Yes, but his third post was asking a question that I think deserved
an answer.

[asetof...@gmail.com]

>Such threads deserve silence
as answer.

Amen