Path: csiph.com!xmission!news.glorb.com!border1.nntp.dca1.giganews.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED!nerds-end
From: Seima Rao <seimarao@gmail.com>
Newsgroups: comp.compilers
Subject: BNF-based HLL code generation & associated user(tool)
Date: Fri, 25 Sep 2015 14:00:31 +0530
Organization: Compilers Central
Lines: 40
Sender: news@iecc.com
Approved: comp.compilers@iecc.com
Message-ID: <15-09-018@comp.compilers>
NNTP-Posting-Host: news.iecc.com
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
X-Trace: miucha.iecc.com 1443380751 97045 2001:470:1f07:1126:0:676f:7373:6970 (27 Sep 2015 19:05:51 GMT)
X-Complaints-To: abuse@iecc.com
NNTP-Posting-Date: Sun, 27 Sep 2015 19:05:51 +0000 (UTC)
Keywords: question, syntax, comment
Posted-Date: 27 Sep 2015 15:05:50 EDT
X-submission-address: compilers@iecc.com
X-moderator-address: compilers-request@iecc.com
X-FAQ-and-archives: http://compilers.iecc.com
Xref: csiph.com comp.compilers:1613

Hi,

    I have a requirement wherein, I would need to implement a tool
    that generates C code from the C grammar. For that matter C++.

    This is unlike what a compiler does.

    The C grammar is embedded inside the tool and some handholding
    (aka menu) would put proper identifiers and context(i.e. particular
    production to generate from).

    The tool will not have anything to do with semantics, though so
    this makes the job easier. No parsing is required.

    My question is , is this top-level generation of language code
    from grammar(by me) & semantics, etc(by anyone) been done
    historically ?

    My basic motive in asking this is to understand, how usefully
    have dimensions internal and external been inputted to
    such "compilers".

    I will give an example:

    Say, I intend to inspect 'C' codes for HLL-driven parallelism
   like EPIC/VLIW, Multithreading.

   Then grossly speaking, a dimension of 'parallelism' and
    then a subdimension of 'IPC' can be input to the tool
   along with other general-purpose inputs which I have mentioned
   earlier. This will allow someone to inspect VLIW C snippets
   via an automated system.

   Before proceeding to implement this tool, I would like your
   help in assimilating if others have attempted before and
   any suggestions that you want to make.

Sincerely,
Seima Rao.
[Sounds sort of like the syntax directed editors that were popular 30 years ago. -John]