This is the Base class of the Extreme class. More...
| Header: | #include <a/base.h> |
| Inherited By: |
| virtual void | abstractBaseMemberFunction1() = 0 |
| virtual void | abstractBaseMemberFunction1(int xyz) = 0 |
| virtual void | abstractBaseMemberFunction1(int xyz) const = 0 |
| virtual void | abstractBaseMemberFunction2() = 0 |
| virtual void | abstractBaseMemberFunction2(int xyz) = 0 |
| virtual void | abstractBaseMemberFunction2(int xyz) const = 0 |
| virtual void | abstractBaseMemberFunction3(int xyz) const = 0 |
| virtual void | abstractBaseMemberFunction4(int xyz) const = 0 |
| virtual void | abstractBaseMemberFunction5(int xyz) const = 0 |
| void | baseMemberFunction1() |
| virtual void | virtualBaseMemberFunction1(int xyz) const |
| void | baseStaticMemberFunction1() |
| virtual void | virtualProtecetdBaseMemberFunction1(int xyz) const |
| virtual void | virtualProtecetdBaseMemberFunction2(int xyz) const = 0 |
| virtual void | virtualProtecetdSlotBaseMemberFunction2(int xyz) const = 0 |
This is the Base class of the Extreme class.
Some other text. To be able to get a feeling for text formating, you need a lot of text to get a feeling for it. So yeah, tadaa! Here's some text. I thnk we need a little more text. A lot more text.
Maybe a new paragraph would be also nice. This filling-text doesn't have to make sense. It joust should be a lot of it. In this case, I prefer Quantity over Quality. That's usually not a good idea when writing a documentation. But for a showcase I think this should be ok.
Is it already eneough filltext? I don't think so. I need more! But where can I get some ideas for a text? I have no idea. Maybe I should tell something about my past. Well there was an apple cake my grandma used to bake. Maybe I should search the recipe? It had a lot of of fruit, so I don't think it was very unhealthy. I think it's time of a linebreak.
Now, that we are already talking about cokkies: Have you ever wondert, why there are some sortsof candy you can only buy for special holidays like christmas. While there are other sorts of cookies you can buy the whole year. I wonder who decided to sell some cookies only for certain holidays. Hmm, probably it wasn't a decision of a single person. It was was a tradicion for some cookies. But then, chockolate, coconuts and vanilla were unknown in europe for centuries. So the tradition must have evolved in the past few centuries.
Well, I think that's eneough text for now. I probably will copy this text, even if it has no meaning for anyone. But hey, that's the idea of it.
This the member function Base::abstractBaseMemberFunction1() of the Base class
Detailed documentation to the Base::abstractBaseMemberFunction1() function
Some other text. To be able to get a feeling for text formating, you need a lot of text to get a feeling for it. So yeah, tadaa! Here's some text. I thnk we need a little more text. A lot more text.
Maybe a new paragraph would be also nice. This filling-text doesn't have to make sense. It joust should be a lot of it. In this case, I prefer Quantity over Quality. That's usually not a good idea when writing a documentation. But for a showcase I think this should be ok.
This the member function Base::abstractBaseMemberFunction1(int) of the Base class
Detailed documentation to the Base::abstractBaseMemberFunction1(int) function with the argument xyz.
Some other text. To be able to get a feeling for text formating, you need a lot of text to get a feeling for it. So yeah, tadaa! Here's some text. I thnk we need a little more text. A lot more text.
Maybe a new paragraph would be also nice. This filling-text doesn't have to make sense. It joust should be a lot of it. In this case, I prefer Quantity over Quality. That's usually not a good idea when writing a documentation. But for a showcase I think this should be ok.
This the member function Base::abstractBaseMemberFunction1(int) const of the Base class
Detailed documentation to the Base::abstractBaseMemberFunction1(int) const function with the argument xyz.
Some other text. To be able to get a feeling for text formating, you need a lot of text to get a feeling for it. So yeah, tadaa! Here's some text. I thnk we need a little more text. A lot more text.
Maybe a new paragraph would be also nice. This filling-text doesn't have to make sense. It joust should be a lot of it. In this case, I prefer Quantity over Quality. That's usually not a good idea when writing a documentation. But for a showcase I think this should be ok.
This the member function Base::abstractBaseMemberFunction2() of the Base class
Detailed documentation to the Base::abstractBaseMemberFunction2() function
Some other text. To be able to get a feeling for text formating, you need a lot of text to get a feeling for it. So yeah, tadaa! Here's some text. I thnk we need a little more text. A lot more text.
Maybe a new paragraph would be also nice. This filling-text doesn't have to make sense. It joust should be a lot of it. In this case, I prefer Quantity over Quality. That's usually not a good idea when writing a documentation. But for a showcase I think this should be ok.
This the member function Base::abstractBaseMemberFunction2(int) of the Base class
Detailed documentation to the Base::abstractBaseMemberFunction2(int) function with the argument xyz.
Some other text. To be able to get a feeling for text formating, you need a lot of text to get a feeling for it. So yeah, tadaa! Here's some text. I thnk we need a little more text. A lot more text.
Maybe a new paragraph would be also nice. This filling-text doesn't have to make sense. It joust should be a lot of it. In this case, I prefer Quantity over Quality. That's usually not a good idea when writing a documentation. But for a showcase I think this should be ok.
This the member function Base::abstractBaseMemberFunction2(int) const of the Base class
Detailed documentation to the Base::abstractBaseMemberFunction2(int) const function with the argument xyz.
Some other text. To be able to get a feeling for text formating, you need a lot of text to get a feeling for it. So yeah, tadaa! Here's some text. I thnk we need a little more text. A lot more text.
Maybe a new paragraph would be also nice. This filling-text doesn't have to make sense. It joust should be a lot of it. In this case, I prefer Quantity over Quality. That's usually not a good idea when writing a documentation. But for a showcase I think this should be ok.
This the member function Base::abstractBaseMemberFunction3(int) const of the Base class
Detailed documentation to the Base::abstractBaseMemberFunction3(int) const function with the argument xyz.
Some other text. To be able to get a feeling for text formating, you need a lot of text to get a feeling for it. So yeah, tadaa! Here's some text. I thnk we need a little more text. A lot more text.
Maybe a new paragraph would be also nice. This filling-text doesn't have to make sense. It joust should be a lot of it. In this case, I prefer Quantity over Quality. That's usually not a good idea when writing a documentation. But for a showcase I think this should be ok.
This the member function Base::abstractBaseMemberFunction4(int) const of the Base class
Detailed documentation to the Base::abstractBaseMemberFunction4(int) const function with the argument xyz.
Some other text. To be able to get a feeling for text formating, you need a lot of text to get a feeling for it. So yeah, tadaa! Here's some text. I thnk we need a little more text. A lot more text.
Maybe a new paragraph would be also nice. This filling-text doesn't have to make sense. It joust should be a lot of it. In this case, I prefer Quantity over Quality. That's usually not a good idea when writing a documentation. But for a showcase I think this should be ok.
This the member function Base::abstractBaseMemberFunction5(int) const of the Base class
Detailed documentation to the Base::abstractBaseMemberFunction5(int) const function with the argument xyz.
Some other text. To be able to get a feeling for text formating, you need a lot of text to get a feeling for it. So yeah, tadaa! Here's some text. I thnk we need a little more text. A lot more text.
Maybe a new paragraph would be also nice. This filling-text doesn't have to make sense. It joust should be a lot of it. In this case, I prefer Quantity over Quality. That's usually not a good idea when writing a documentation. But for a showcase I think this should be ok.
This the member function Base::baseMemberFunction1() const of the Base class
Detailed documentation to the Base::baseMemberFunction1() const function with the argument.
Some other text. To be able to get a feeling for text formating, you need a lot of text to get a feeling for it. So yeah, tadaa! Here's some text. I thnk we need a little more text. A lot more text.
Maybe a new paragraph would be also nice. This filling-text doesn't have to make sense. It joust should be a lot of it. In this case, I prefer Quantity over Quality. That's usually not a good idea when writing a documentation. But for a showcase I think this should be ok.
This the member function Base::baseStaticMemberFunction1() const of the Base class
Detailed documentation to the Base::baseStaticMemberFunction1() const function with the argument.
Some other text. To be able to get a feeling for text formating, you need a lot of text to get a feeling for it. So yeah, tadaa! Here's some text. I thnk we need a little more text. A lot more text.
Maybe a new paragraph would be also nice. This filling-text doesn't have to make sense. It joust should be a lot of it. In this case, I prefer Quantity over Quality. That's usually not a good idea when writing a documentation. But for a showcase I think this should be ok.
This the member function Base::virtualBaseMemberFunction1(int) const of the Base class
Detailed documentation to the Base::virtualBaseMemberFunction1(int) const function with the argument xyz.
Some other text. To be able to get a feeling for text formating, you need a lot of text to get a feeling for it. So yeah, tadaa! Here's some text. I thnk we need a little more text. A lot more text.
Maybe a new paragraph would be also nice. This filling-text doesn't have to make sense. It joust should be a lot of it. In this case, I prefer Quantity over Quality. That's usually not a good idea when writing a documentation. But for a showcase I think this should be ok.
This the member function Base::virtualProtecetdBaseMemberFunction1(int) const of the Base class
Detailed documentation to the Base::virtualProtecetdBaseMemberFunction1(int) const function with the argument xyz.
Some other text. To be able to get a feeling for text formating, you need a lot of text to get a feeling for it. So yeah, tadaa! Here's some text. I thnk we need a little more text. A lot more text.
Maybe a new paragraph would be also nice. This filling-text doesn't have to make sense. It joust should be a lot of it. In this case, I prefer Quantity over Quality. That's usually not a good idea when writing a documentation. But for a showcase I think this should be ok.
This the member function Base::virtualProtecetdBaseMemberFunction1(int) const of the Base class
Detailed documentation to the Base::virtualProtecetdBaseMemberFunction1(int) const function with the argument xyz.
Some other text. To be able to get a feeling for text formating, you need a lot of text to get a feeling for it. So yeah, tadaa! Here's some text. I thnk we need a little more text. A lot more text.
Maybe a new paragraph would be also nice. This filling-text doesn't have to make sense. It joust should be a lot of it. In this case, I prefer Quantity over Quality. That's usually not a good idea when writing a documentation. But for a showcase I think this should be ok.
This the member function Base::virtualProtecetdSlotBaseMemberFunction2(int) const of the Base class
Detailed documentation to the Base::virtualProtecetdSlotBaseMemberFunction2(int) const function with the argument xyz.
Some other text. To be able to get a feeling for text formating, you need a lot of text to get a feeling for it. So yeah, tadaa! Here's some text. I thnk we need a little more text. A lot more text.
Maybe a new paragraph would be also nice. This filling-text doesn't have to make sense. It joust should be a lot of it. In this case, I prefer Quantity over Quality. That's usually not a good idea when writing a documentation. But for a showcase I think this should be ok.