Guido Wolf Reichert

icon indicating a website link https://bsl-support.de icon indicating an email [email protected]

icon company @bslMS icon location Kiel, Germany icon location Management Consultant with a solid background in OR/MS. I specialize in using simulation models to tackle strategic and operational management issues.

Results 49 comments of Guido Wolf Reichert

Type checking versus unit checking

> > Make no mistake: It is absolutely essential that `unit` errors are caught (e.g., as to not mix `mm` and `m` in Quentins example in #3381). But to me...

Type checking versus unit checking

Thinking about this a bit more, I believe I should find myself corrected with regard to `quantity` for (at least) _causal_ connectors. From a philosophical point of view the `quantity`...

Type checking versus unit checking

Excellent comment to be linked from here: https://github.com/modelica/ModelicaSpecification/issues/2127#issuecomment-1271723893

Experiment annotations have no effect in OMJulia

@arun3688 why is this issue still open?

Avoid line breaking just before closing parenthesis

... the sentence also looks grammatically awkward to me. If content needs to be kept I suggest: >For any use of `OldClass` or elements thereof report ...

Lack of standard for deriving connect-Line style from connector icon

Just being curious: What about something like `Modelica.Blocks.Interfaces.RealVectorInput`?

Preserve top-of-file SPDX headers (e.g., REUSE compliance)

I'm not convinced—here's why: - **One file, one class.** Almost every non-trivial library maps one class/type per .mo file. - **Tool access.** Developers work in IDEs and CLIs, not just...

Preserve top-of-file SPDX headers (e.g., REUSE compliance)

Hans, thanks for digging up that old discussion—but it’s from over eight years ago (“an eternity” in software engineering!). In the meantime, best practices have evolved. For example, the GNU...

Preserve top-of-file SPDX headers (e.g., REUSE compliance)

### Minimum requirement As an open-source developer, I must **be able to** insert SPDX headers and related legal information—either in a block comment (`/* … */`) or as a series...

Preserve top-of-file SPDX headers (e.g., REUSE compliance)

@beutlich Thanks. But is there a guarantee that the comment is a) pre-served and b) not relocated to a different position given that comments are treated as whitespace according to...