[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Phoenix language
From: |
Dr. H. Nikolaus Schaller |
Subject: |
Re: Phoenix language |
Date: |
Thu, 23 Oct 2014 10:03:12 +0200 |
Paraphrasing David’s question to my objc-interpreter a little gives another
question…
Am 23.10.2014 um 09:39 schrieb Dr. H. Nikolaus Schaller <hns@computer.org>:
> Let me add some more questions to better understand the details of the
> Phoenix project. So that I am enabled (and maybe others) to positively
> contribute on the technical side:
>
> * what is the target of the compiler output? I could imagine Obj-C,
> Assembler, C++, Java or JavaScript but don’t know.
> * could you take the AST code from the ObjCKit.framework of mySTEP?
> * could you make it compatible to use the same pipeline, i.e. make Phoenix
> a frontend for a common AST framework/library and backends?
> * what is the rationale to write it in Obj-C if Swift tries to supersede it?
> * what is the problem with lex/bison (I didn’t understand David’s concerns)?
* what arguments are pro and con writing a new language frontend for the
exsiting compiler collections gcc or clang/llvm or writing something from
scratch (Phoenix)?
BR,
Nikolaus
- Re: Phoenix language, (continued)
- Re: Phoenix language, Dr. H. Nikolaus Schaller, 2014/10/22
- Re: Phoenix language, Ivan Vučica, 2014/10/22
- Re: Phoenix language, Dr . H . Nikolaus Schaller, 2014/10/23
- Re: Phoenix language, David Chisnall, 2014/10/23
- Re: Phoenix language, Dr. H. Nikolaus Schaller, 2014/10/23
- Re: Phoenix language, Gregory Casamento, 2014/10/22
- Re: Phoenix language, Gregory Casamento, 2014/10/22
- Re: Phoenix language, Dr. H. Nikolaus Schaller, 2014/10/23
- Re: Phoenix language,
Dr. H. Nikolaus Schaller <=
- Re: Phoenix language, Gregory Casamento, 2014/10/23
- Re: Phoenix language, Gregory Casamento, 2014/10/23
- Re: Phoenix language, Dr. H. Nikolaus Schaller, 2014/10/23
Re: Phoenix language, Gregory Casamento, 2014/10/22