: [generation] Another approach to generated drivers
Hi All,
to answer Niclas' question first ... yes a lot of tools allow writing code in
for example Java and have that compiled to c-like programs.
I had a look at a lot of these options before starting to work on PLC4X and
continued since then.
Hi,
thanks!
Of course the Paper will only speak about the project in regular 3rd person
view so I see no issue for policy violations.
Julian
Am 29.04.19, 13:20 schrieb "Justin Mclean" :
Hi,
> But, I guess we get rid of the discussion if we do the following
> - generate a PLC4
Hi,
> But, I guess we get rid of the discussion if we do the following
> - generate a PLC4X branch where all the development takes place (=>
> everything is ASF licensed)
> - keep the paper source in the separate repo and, if necessary, reference
> code snippets from PLC4X Repo (with clear licen
Hi Justin,
I see your concerns and I agree that I still have to learn some things about
the "Apache Way" and this "do it all in the open" philosophy, thus this is a
good discussion.
But, I guess we get rid of the discussion if we do the following
- generate a PLC4X branch where all the developme
Hi,
> some clarification... this repo currently hosts two things... some code
> snippets (really messy) and the draft version for the paper (like really
> really early draft).
If any of the code appears in the paper and is not clearly licensed under a
compatible license then it’s unlikely PLC4
Hi Justin,
some clarification... this repo currently hosts two things... some code
snippets (really messy) and the draft version for the paper (like really really
early draft).
The paper code is what is (for me) unsure license related but the code will of
course go to the PLC4X repo (once it is
Hi,
> And for the private Repo... It also felt wrong for me to write this. And
> strictly speaking its not a PLC4X Paper but a Paper which "talks about"
> PLC4X. The main reason for the private repo are license concerns as the
> authors usually have to hand over several rights to the Publisher
Hi Julian,
I'm totally fine with that ;-)
Chris
Am 29.04.19, 10:43 schrieb "Julian Feinauer" :
Hi Chris,
Hi Niclas,
@Niclas:
Basically Chris answered all those questions as I would. I also looked at
Meta Languages like Haxe but there usually where some drawbacks.
B
Hi Chris,
Hi Niclas,
@Niclas:
Basically Chris answered all those questions as I would. I also looked at Meta
Languages like Haxe but there usually where some drawbacks.
But what we discussed was the idea to generate the DSL or the AST from python
code (very limited python code), so that our DSL
Hi All,
to answer Niclas' question first ... yes a lot of tools allow writing code in
for example Java and have that compiled to c-like programs.
I had a look at a lot of these options before starting to work on PLC4X and
continued since then.
I was never quite happy with the results. While th
Outsider looking in; Many language runtimes allows embedding of other
languages' runtimes within. So why not pick a languages that is reasonably
easy to integrate into other languages, and then write the drivers in a
fully fledged programming language, rather than the DFDL abstraction or
creating a
Hi all,
just wanted to sum up some talks and discussions we had off-list about the
whole topic of driver generation / providing drivers in other languages.
Currently, there are the following two approaches going on:
Driver Generation based on DFDL by Chris:
Chris already shared his branch and is
12 matches
Mail list logo
