Re: [GSoC 2016] Java source code to Scala.js IR compiler

Naftoli Gugenheim <[email protected]> Tue, 15 Mar 2016 12:21:47 +0000
Newsgroups gmane.comp.lang.scala
Message-ID <CANpg8PDWvPZC+yT0LCig3gu-=X7EppH-ONR-H9U8YjDyeETmLg@mail.gmail.com>
Have you seen JSweet?

On Tue, Mar 15, 2016, 6:36 AM Sébastien Doeraene <[email protected]>
wrote:

> Hello Piotr,
>
> Sorry for the late answer. The past week has been crazy with work and
> concerts.
>
> For reusing existing parsers/typecheckers, it has been brought to my
> attention that the new Android tool chain [1] uses the Eclipse Java
> Compiler (ECJ), so that would be something to explore.
>
> I don't really have more ideas at the moment. The expectations are that we
> can actually compile non-trivial Java libraries into the IR and so reuse
> them in Scala.js applications. But I don't expect that *any* Java code can
> be compiled. In particular, I have serious doubts about class initializers.
>
> See also another discussion on the mailing list about this project at
> https://groups.google.com/forum/#!topic/scala-language/lPn8f4L0wkw
>
> Cheers,
> Sébastien
>
> [1] http://tools.android.com/tech-docs/jackandjill
>
> On Wed, Mar 9, 2016 at 9:50 PM, Piotr Moczurad <[email protected]>
> wrote:
>
>> Hello,
>>
>> I'm writing to ask about the "Java source code (or bytecode) to Scala.js
>> IR compiler" project. I have some experience in both Scala language (and
>> functional programming in general) and compiler design/implementation, so I
>> thought I could be a good fit for the project.
>>
>> My name is Piotr Moczurad and I'm a fourth-year CS student at AGH
>> University of Science and Technology in Kraków and a first-year math
>> student at the Jagiellonian University. I took part in GSoC 2014, writing
>> some parts of Gust (GPU extensions for the Breeze Scala linalg library). I
>> wish I had continued to develop this project, but I got involved with
>> Haskell programming and then mathematics. On the bright side, this allowed
>> me to improve my functional programming skills quite considerably.
>>
>> I was working at a company creating image compositing software powered by
>> our own in-house visual-textual programming language, which was a lot of
>> fun tinkering with the compiler (I'm particularily proud of the transparent
>> Python-Haskell bindings that I created and unfortunately cannot
>> open-source). As far as my compiler-related experience goes, I also
>> recently finished a BS project involving writing a simple programming
>> language, targeting  an FPGA-based soft processor which we also designed
>> and implemented from the scratch. It contains some possibly interesting
>> ideas regarding generating an architecture-targeted assembly and
>> stack-machine design.
>>
>> I'd love to hear more about this project; I think I could contribute some
>> interesting things. I would much rather go with implementing the
>> Java-source-code-to-IR option -- reusing parsers/typechecker sounds like a
>> good plan (I have no problem in writing my own, however the essence of the
>> problem is, I guess, the IR generation/optimization and the time is
>> limited). I would love to hear more about your ideas and expectations.
>>
>> I'm looking forward to hearing from you!
>>
>> Regards,
>> Piotr Moczurad
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "scala-language" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "scala-language" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "scala-language" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.