From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Application of model-driven engineering?
Date: Mon, 29 Oct 2012 12:50:08 +0100 [thread overview]
Message-ID: <508E6D70.5060207@users.sourceforge.net> (raw)
In-Reply-To: <CAAxaTiNPSj=xexkp90cu-8asVbMxnt04O39hmXrQN4zoZHutgQ@mail.gmail.com>
> If you need to improve Coccinelle, learn OCaml.
I suggest to consider additional design techniques for further software
development. I imagine that tools which support model-driven engineering
help in the documentation and exchange for useful ideas.
Will the probability for valuable contributions increase if knowledge
requirements can be adjusted for recommended programming languages?
Do you see also chances in transformations between platform-independent
and platform-specific models?
Regards,
Markus
prev parent reply other threads:[~2012-10-29 11:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 22:03 [Cocci] spatches for cpp? ron minnich
2012-10-25 11:19 ` Julia Lawall
2012-10-26 10:55 ` [Cocci] semantic patches for C preprocessing constructs? SF Markus Elfring
2012-10-26 13:47 ` Julia Lawall
2012-10-28 9:14 ` SF Markus Elfring
2012-10-28 12:14 ` Julia Lawall
2012-10-28 16:02 ` SF Markus Elfring
2012-10-29 8:28 ` Nicolas Palix
2012-10-29 11:50 ` SF Markus Elfring [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=508E6D70.5060207@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=cocci@systeme.lip6.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox