k-user AT lists.cs.illinois.edu

Subject: K-user mailing list

List archive

[[K-user] ] benefit of fully-bracketed concrete syntax for evaluating K?

From: Dustin Wehr <dustin.wehr AT gmail.com>
To: k-user AT lists.cs.illinois.edu
Subject: [[K-user] ] benefit of fully-bracketed concrete syntax for evaluating K?
Date: Wed, 10 Apr 2019 13:20:55 -0400
Authentication-results: illinois.edu; spf=pass smtp.mailfrom=dustin.wehr AT gmail.com; dkim=pass header.d=gmail.com header.s=20161025; dmarc=pass header.from=gmail.com

For the purpose of evaluating the suitability of K for my company's
use case, I am wondering if I should expect to have an easier time
formalizing a fully-bracketed concrete syntax for our language (well,
for a minimal version of our language, but that's not what I'm asking
about). I understand that the general recommendation is to use one's
desired concrete syntax, but I don't think we need to use a nice
syntax at this stage in order to imagine what it will be like to later
have a K formalization that uses a nice syntax.

Thanks,
Dustin Wehr

[[K-user] ] benefit of fully-bracketed concrete syntax for evaluating K?, Dustin Wehr, 04/10/2019
- Re: [[K-user] ] benefit of fully-bracketed concrete syntax for evaluating K?, Dwight Guth, 04/10/2019