@@ -57,18 +57,15 @@ Application Note: Object-Oriented Programming in C
@endhtmlonly
-
@subsection lightweight Lightweight
The most unique characteristic of the QP/C™ framework is its very small footprint, especially in RAM. In this respect, QP/C™ requires less resources than even the smallest conventional Real-Time Operating System (RTOS) kernel. At the same time, QP gives you a much higher level of abstraction than a conventional RTOS. With QP, you work at the level of active objects, state machines and events, as opposed to "naked" threads of an RTOS.
-
@subsection hsms Hierarchical State Machines
-The behavior of active objects is specified in QP by means of
-
hierarchical state machines (UML statecharts). The framework supports @ref sm "manual coding of UML state machines in C" (or C++ in case of QP/C++) as well as fully **automatic code generation** by means of the free graphical
QM™ model-based design (MBD) tool.
+The behavior of active objects is specified in QP/C by means of
hierarchical state machines (UML statecharts). The framework supports @ref sm "manual coding of UML state machines in C" (or C++ in case of QP/C++) as well as fully **automatic code generation** by means of the free graphical
QM™ model-based design (MBD) tool.
@remarks
-State machines can be an incredibly powerful technique, but they require an event-driven **infrastructure** (framework) that provides, at a minimum: a run-to-completion (RTC) execution context for each state machine, queuing of events, and event-based timing services. This is really the pivotal point. Without an event-driven framewok (like QP/C), state machines are like
cars without an infrastructure of roads.
+State machines can be an incredibly powerful technique, but they require an event-driven **infrastructure** (framework) that provides, at a minimum: a run-to-completion (RTC) execution context for each state machine, queuing of events, and event-based timing services. This is really the pivotal point. Without an event-driven framework (like QP/C), state machines are like
cars without an infrastructure of roads.
@subsection kernels Built-in Kernels
@@ -80,7 +77,7 @@ QP/C can also work with many traditional @ref exa_rtos "RTOSes" and @ref exa_rto
@subsection popular Popularity & Maturity
-With over 15 years of continuous development and
60,000 downloads a year, the QP™ RTEF family is the most mature and popular such solution on the embedded software market. The QP™ frameworks are used in
millions of products worldwide in medical devices, consumer electronics, wired and wireless telecommunications, industrial automation, transportation, aerospace, robotics, and many more.
+With over 15 years of continuous development and
60,000 downloads a year, the QP™ RTEF family is the most mature and popular such solution on the embedded software market. The QP™ frameworks are used in
millions of products worldwide in medical devices, consumer electronics, wired and wireless telecommunications, industrial automation, transportation, aerospace, robotics, and many more.
@subsection psicc2 Book
@@ -90,17 +87,17 @@ The book,
dual licensing model, in which both the open source software distribution mechanism and traditional closed source software distribution models are combined.
+QP/C is licensed under the sustainable
dual licensing model, in which both the open source software distribution mechanism and traditional closed source software distribution models are combined.
@note If your company has a policy forbidding open source in your product, all QP frameworks can be licensed commercially, in which case you don't use any open source license and you do not violate your policy.
@subsection open-source Open Source Projects
-If you are developing and distributing open source applications under the GNU General Public License (GPL), as published by the Free Software Foundation, then you are free to use the Quantum Leaps software under the
GPL version 3 of the License, or (at your option) any later version. Please note that GPL requires that all modifications to the original code as well as your application code (Derivative Works as defined in the Copyright Law) must also be released under the terms of the GPL open source license.
+If you are developing and distributing **open source** applications under the GNU General Public License (GPL), as published by the Free Software Foundation, then you are free to use the Quantum Leaps software under the
GPL version 3 of the License, or (at your option) any later version. Please note that GPL requires that all modifications to the original code as well as your application code (Derivative Works as defined in the Copyright Law) must also be released under the terms of the GPL open source license.
@subsection closed-source Closed Source Projects
-If you are developing and distributing traditional closed source applications, you can purchase one of
Quantum Leaps commercial licenses, which are specifically designed for users interested in retaining the proprietary status of their code. All Quantum Leaps commercial licenses expressly supersede the GPL open source license. This means that when you license Quantum Leaps software under a commercial license, you specifically do not use the software under the open source license and therefore you are not subject to any of its terms.
+If you are developing and distributing traditional **closed source** applications, you can purchase one of
Quantum Leaps commercial licenses, which are specifically designed for users interested in retaining the proprietary status of their code. All Quantum Leaps commercial licenses expressly supersede the GPL open source license. This means that when you license Quantum Leaps software under a commercial license, you specifically do not use the software under the open source license and therefore you are not subject to any of its terms.
@section support How to get help?
@@ -115,7 +112,7 @@ Training and consulting services are also available from Quantum Leaps. Please r
- Quantum Leaps Web site:
state-machine.com
-- Quantum Leaps licensing:
state-machine.com/licensing
+- Quantum Leaps licensing:
state-machine.com/licensing
- QP/QM on SourceForge.net:
sourceforge.net/projects/qpc
diff --git a/doxygen/srs.dox b/doxygen/srs.dox
index 3d0bcf7a..4f9447c9 100644
--- a/doxygen/srs.dox
+++ b/doxygen/srs.dox
@@ -84,7 +84,7 @@ Requirement definitions use consistent terminology to indicate whether something
@section srs_qep State Machine Event Processor (QEP)
-The QP/C Event Processor (QEP) is a sub-component of the QP/C framework that implements processing of events according to state machine machine semantics. Specifically, according to that semantics each event is processed to completion (Run-to-Completion) before the processing of the next event can begin.
+The QP/C Event Processor (QEP) is a sub-component of the QP/C framework that implements processing of events according to state machine semantics. Specifically, according to that semantics each event is processed to completion (Run-to-Completion) before the processing of the next event can begin.
@reqdef{RQPC101} QEP shall process events according to the Run-To-Completion (RTC) semantics.