Skip to content

Fix links #311

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

Merged
merged 2 commits into from
Jun 6, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/developer/regression-tests.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ description: Regression Tests for Lingua Franca.

Lingua Franca comes with an extensive set of regression tests that are executed on various platforms automatically whenever an update is pushed to the LF repository. There are two categories of tests:

- **Unit tests** are Java or Kotlin methods in our code base that are labeled with the `@Test` directive. These tests check individual functions of the code generation infrastructure. These are located in the `src/test` directory of each subproject within the repository.
- **Unit tests** are Java methods in our code base that are labeled with the `@Test` directive. These tests check individual functions of the code generation infrastructure. These are located in the `core/src/test` directory.
- **Integration tests** are complete Lingua Franca programs that are compiled and executed automatically. A test passes if it successfully compiles and runs to completion with normal termination (return code 0). These tests are located in the `test` directory at the root of the LF repo, with one subdirectory per target language.
Their implementation can be found in the `core/src/integrationTest` directory.
The integration tests are also executed through JUnit using methods with `@Test` directives, but they are executed separately.
Expand All @@ -26,7 +26,7 @@ You can specify any valid target. If you run the task without specifying the tar

The `targetTest` task is essentially a convenient shortcut for the following:
```
./gradew core:integrationTest --test org.lflang.tests.runtime.<target>Test.*
./gradlew core:integrationTest --tests "org.lflang.tests.runtime.<target>Test.*"
```
If you prefer have more control over which tests are executed, you can also use this more verbose version.

Expand Down
4 changes: 3 additions & 1 deletion docs/reference/target-declaration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,8 @@ import {

<LanguageSelector c cpp py rs ts />

# Target Declaration

Every Lingua Franca program begins with a statement of this form:

```lf
Expand All @@ -19,7 +21,7 @@ Every Lingua Franca program begins with a statement of this form:

The `<name>` gives the name of some Lingua Franca target language, which is the language in which reactions are written. This is also the language of the program(s) generated by the Lingua Franca compiler. The target languages currently supported are C, C++, Python, TypeScript, and Rust. There is also a target CCpp that is just like the C target except that it uses a C++ compiler to compile the code, thereby allowing inclusion of C++ code.

# Summary of Parameters
# Summary of Target Parameters

A target specification may have optional parameters, the names and values of which depend on which specific target you are using. Each parameter is a key-value pair, where the supported keys are a subset of the following:

Expand Down
73 changes: 34 additions & 39 deletions docs/reference/target-language-details.mdx

Large diffs are not rendered by default.

7 changes: 1 addition & 6 deletions docs/writing-reactors/reactions.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ Reactions may optionally be named. The name is cosmetic and may serve as additio

The reaction's behavior is defined by its body, which should be given in the target programming language. Note that the reaction body may only read from actions and ports that it has declared as triggers or uses, and it may only write to actions and ports that it has declared as an effect. The target code generators implement a scoping mechanism, such that only variables that are declared in the reaction signature are accessible in the reaction body.

In some targets, the reaction body may be omitted and the body can be defined natively in the target language in an external file. See the section on [Bodyless Reactions](#bodyless-reactions) for details.
In some targets, the reaction body may be omitted and the body can be defined natively in the target language in an external file. See the section on [Reaction Declarations](./reaction-declarations.mdx) for details.

## Reaction Order

Expand Down Expand Up @@ -124,8 +124,3 @@ For details, see the [Modal Reactors](../writing-reactors/modal-models.mdx) sect

</ShowIf>
</ShowIfs>


## Bodyless Reactions

See [Reaction Declarations](./reaction-declarations.mdx).
56 changes: 28 additions & 28 deletions versioned_docs/version-0.5.0/reference/target-language-details.mdx

Large diffs are not rendered by default.

56 changes: 28 additions & 28 deletions versioned_docs/version-0.6.0/reference/target-language-details.mdx

Large diffs are not rendered by default.

56 changes: 28 additions & 28 deletions versioned_docs/version-0.7.0/reference/target-language-details.mdx

Large diffs are not rendered by default.

56 changes: 28 additions & 28 deletions versioned_docs/version-0.8.0/reference/target-language-details.mdx

Large diffs are not rendered by default.

56 changes: 28 additions & 28 deletions versioned_docs/version-0.9.0/reference/target-language-details.mdx

Large diffs are not rendered by default.