Skip to Content.
Sympa Menu

k-user - Re: [K-user] Templating / Macros

k-user AT lists.cs.illinois.edu

Subject: K-user mailing list

List archive

Re: [K-user] Templating / Macros


Chronological Thread 
  • From: "Rosu, Grigore" <grosu AT illinois.edu>
  • To: Suminda Dharmasena <sirinath AT sakrio.com>, "k-user AT cs.uiuc.edu" <k-user AT cs.uiuc.edu>, "info AT kframework.org" <info AT kframework.org>
  • Subject: Re: [K-user] Templating / Macros
  • Date: Fri, 3 Jan 2014 13:14:52 +0000
  • Accept-language: en-US
  • List-archive: <http://lists.cs.uiuc.edu/pipermail/k-user/>
  • List-id: <k-user.cs.uiuc.edu>

Suminda and others,

Let us please try to keep the traffic on the k-user list minimal and strictly related to issues that would interest all the K users, or to questions that other users of K may have answers to.

Don't take me wrong: your suggestions are welcome and very interesting to us, the designers and developers of K (I particularly liked the visualization of Python executions and started thinking about how to have something similar for K).  But the best place to post these is the K github issues, not on the k-user list, I think.

Thank you,
Grigore
 
 

From: Suminda Dharmasena [sirinath AT sakrio.com]
Sent: Friday, January 03, 2014 5:45 AM
To: k-user AT cs.uiuc.edu; Rosu, Grigore; info AT kframework.org
Subject: Re: Templating / Macros

Another case would be that if I want to create a language influenced by other language for which there are K semantics, how to select all this into the new language and override parts relative to the new language. Some of this may involve transformations where syntax and rules are similar but not exact. 

Tempting can be used where you leave out stuff to be filled in later. Transformations can be used to take what is there and fit it to a new usage.

Problem with above is complex interactions between syntax and rules. So templating, overriding and transformations should not break the new language or create something inconsistent. 



Archive powered by MHonArc 2.6.16.

Top of Page