From geertjan at apache.org Fri Feb 7 11:58:35 2020 From: geertjan at apache.org (Geertjan Wielenga) Date: Fri, 7 Feb 2020 12:58:35 +0100 Subject: @Language annotation for JDK 13 text blocks Message-ID: Hi all, It would be of great support for IDEs, editors, and tools of various kinds if a @Language annotation would be part of the support for text blocks, so that tooling would be able to determine which editor should be injected within the text block. For example, imagine this annotation on top of a text block: @Language="text/html" That would then be used by IDEs, editors, tools, etc, to determine that the text within the block is HTML and that therefore, for the tools that support this (e.g., NetBeans, IntelliJ IDEA), an HTML editor would then be injected within the text block, which would make HTML-oriented syntax coloring, code completion, etc, available within the text block. If this meets with enthusiasm, what would the next steps be? An addition to the text block spec or a new spec or something different? Thanks, Geertjan From lp.edoardo at gmail.com Fri Feb 7 12:34:16 2020 From: lp.edoardo at gmail.com (Edoardo Luppi) Date: Fri, 7 Feb 2020 13:34:16 +0100 Subject: @Language annotation for JDK 13 text blocks In-Reply-To: References: Message-ID: Hi! Mmh I have mixed feelings about this. Most people I've met, plus me in this case, prefer to use comment-based injection (// language=LANG_ID) as comments are less noticeable than Annotations. Also, I don't think introducing this new Annotation in java.lang (I suppose) is appropriate and maybe adding complexity to the spec isn't worth it. On the other hand, as of now sharing in-code language injection metadata is difficult because Annotations are tied to the IDE/editor, which means explicitly imported, e.g. from org.intellij.lang.annotations.Language. In the worst case scenario you'd have multiple Annotations specified for the same string literal, one per IDE/editor, or a mixture of Annotations and comments. Standardizing how injection is to be described could be a good thing! And not only for text blocks. Just my two cents. Thanks! Edoardo On Fri, Feb 7, 2020 at 12:59 PM Geertjan Wielenga wrote: > Hi all, > > It would be of great support for IDEs, editors, and tools of various kinds > if a @Language annotation would be part of the support for text blocks, so > that tooling would be able to determine which editor should be injected > within the text block. > > For example, imagine this annotation on top of a text block: > > @Language="text/html" > > That would then be used by IDEs, editors, tools, etc, to determine that the > text within the block is HTML and that therefore, for the tools that > support this (e.g., NetBeans, IntelliJ IDEA), an HTML editor would then be > injected within the text block, which would make HTML-oriented syntax > coloring, code completion, etc, available within the text block. > > If this meets with enthusiasm, what would the next steps be? An addition to > the text block spec or a new spec or something different? > > Thanks, > > Geertjan > From waltimlmm at gmail.com Tue Feb 11 20:12:33 2020 From: waltimlmm at gmail.com (walter lucas) Date: Tue, 11 Feb 2020 17:12:33 -0300 Subject: Investigating the benefits and implications of using lambda expressions in Java programs Message-ID: Dear all, I'm a Ph.D. student at the University of Bras?lia (UNB), Brazil. We are currently investigating the benefits and implications of using lambda expressions in Java programs so that we could later improve existing tools that automatically refactor legacy code to introduce lambda expressions. As part of our research, we are conducting a survey that collects the developers' perceptions of a couple of transformations recommended by tools to refactor either an anonymous inner class or a for-loop into lambda expressions and streams. It would be of great help if you could answer this survey, which does not take too much time (5 minutes on average). Your participation is voluntary and confidential. You might withdraw at any time. The link for the survey is http://qarefactoring.com/ We will make our results (data sets, data analysis, and tools) publicly available. Thank you so much for your time, and please do not hesitate to contact me if you have any questions. Thanks in advance! -- Att Walter Lucas. From maurizio.cimadamore at oracle.com Wed Feb 12 01:27:33 2020 From: maurizio.cimadamore at oracle.com (Maurizio Cimadamore) Date: Wed, 12 Feb 2020 01:27:33 +0000 Subject: RFR [15] 8238918 idea.sh should work with both mercurial and git repo In-Reply-To: References: Message-ID: <8752c359-05e8-15ee-c57e-21431391d4c2@oracle.com> Looks good! Thanks Maurizio On 11/02/2020 22:29, Roger Riggs wrote: > Please review a small change to the idea.sh script that generates an > IntelliJ project. > It detects either Mercurial or Git repos and generates the appropriate > vcs.xml. > > Webrev: > ?? http://cr.openjdk.java.net/~rriggs/webrev-idea-git-8238918/ > > Issue: > ? https://bugs.openjdk.java.net/browse/JDK-8238918 > > Thanks, Roger > From Roger.Riggs at oracle.com Tue Feb 11 22:29:39 2020 From: Roger.Riggs at oracle.com (Roger Riggs) Date: Tue, 11 Feb 2020 17:29:39 -0500 Subject: RFR [15] 8238918 idea.sh should work with both mercurial and git repo Message-ID: Please review a small change to the idea.sh script that generates an IntelliJ project. It detects either Mercurial or Git repos and generates the appropriate vcs.xml. Webrev: ?? http://cr.openjdk.java.net/~rriggs/webrev-idea-git-8238918/ Issue: ? https://bugs.openjdk.java.net/browse/JDK-8238918 Thanks, Roger From erik.joelsson at oracle.com Tue Feb 11 22:40:34 2020 From: erik.joelsson at oracle.com (Erik Joelsson) Date: Tue, 11 Feb 2020 14:40:34 -0800 Subject: RFR [15] 8238918 idea.sh should work with both mercurial and git repo In-Reply-To: References: Message-ID: <3bc7f26a-3122-95a0-ffff-e3406702548a@oracle.com> Looks good. /Erik On 2020-02-11 14:29, Roger Riggs wrote: > Please review a small change to the idea.sh script that generates an > IntelliJ project. > It detects either Mercurial or Git repos and generates the appropriate > vcs.xml. > > Webrev: > ?? http://cr.openjdk.java.net/~rriggs/webrev-idea-git-8238918/ > > Issue: > ? https://bugs.openjdk.java.net/browse/JDK-8238918 > > Thanks, Roger > From lance.andersen at oracle.com Wed Feb 12 11:57:28 2020 From: lance.andersen at oracle.com (Lance Andersen) Date: Wed, 12 Feb 2020 06:57:28 -0500 Subject: RFR [15] 8238918 idea.sh should work with both mercurial and git repo In-Reply-To: References: Message-ID: <5258519C-1E64-4FFD-9D6A-924EAC2B6C24@oracle.com> +1 > On Feb 11, 2020, at 5:29 PM, Roger Riggs wrote: > > Please review a small change to the idea.sh script that generates an IntelliJ project. > It detects either Mercurial or Git repos and generates the appropriate vcs.xml. > > Webrev: > http://cr.openjdk.java.net/~rriggs/webrev-idea-git-8238918/ > > Issue: > https://bugs.openjdk.java.net/browse/JDK-8238918 > > Thanks, Roger > Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037 Oracle Java Engineering 1 Network Drive Burlington, MA 01803 Lance.Andersen at oracle.com From erik.helin at oracle.com Wed Feb 12 07:15:36 2020 From: erik.helin at oracle.com (Erik Helin) Date: Wed, 12 Feb 2020 07:15:36 -0000 Subject: RFR [15] 8238918 idea.sh should work with both mercurial and git repo In-Reply-To: References: Message-ID: <8a7f70dc-96e2-cda6-e1dc-f41d86aee78b@oracle.com> On 2/11/20 11:29 PM, Roger Riggs wrote: > Please review a small change to the idea.sh script that generates an > IntelliJ project. > It detects either Mercurial or Git repos and generates the appropriate > vcs.xml. > > Webrev: > ?? http://cr.openjdk.java.net/~rriggs/webrev-idea-git-8238918/ Looks good! Thanks, Erik