<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">This might be a long-shot (they want it aimed at practitioners), but it might be possible.<div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div>Kim</div><div><br></div></span><br class="Apple-interchange-newline">
</div><div>============================================================================<br>IEEE Software Special Issue on "New Directions in Programming Languages"<br><br> Submission Deadline: 1 February 2014<br> Publication: September/October 2014<br><br> Guest editors: Laurence Tratt and Adam Welc<br>============================================================================<br><br>Computer programming as we know it today has a fairly long history. Fortran<br>was one of the first programming languages created and is still used today.<br>Why, though, isn't all programming today done in Fortran and other languages<br>of its era? One major reason is the diversification of those who want, or<br>need to program. Consequently, programming languages have evolved to satisfy<br>a diverse range of requirements for many different groups of programmers:<br>from professionals working for large software companies, through biologists,<br>chemists and physicists, to graphics designers and teenagers writing<br>applications for Android or iPhone. Furthermore, everyone wants their<br>software to run fast and modern programming languages must offer programmers<br>the ability to maximize utilization of the underlying hardware, which today<br>is often multi-core, many-core, or even heterogeneous.<br><br>In this special edition of IEEE Software, "What's New in Programming<br>Languages?", we are looking for contributions describing how modern<br>programming languages cope with the challenges posed by varied requirements<br>from different programmer groups, combined with the rapid evolution of<br>hardware platforms.<br><br>All submissions must take the form of case studies of language use, design<br>and/or implementation. Negative experiences (regarding features or<br>implementations that did not work well in practice) are welcome, as are<br>positive results. Submissions which show how cross-discipline issues (for<br>example, software/hardware interactions; implications of programming<br>languages for other disciplines) have been addressed in practice are also<br>welcome.<br><br>As long as they meet the requirements above, submissions may take on topics<br>including, but not limited to:<br>* novel programming language features<br>* multiparadigm programming languages, such as Scala, C# or F#<br>* dynamic/scripting programming languages designed for productivity, such as<br>JavaScript, Lua or Python<br>* domain-specific languages (DSLs)<br>* concurrent and parallel programming languages, such as Cilk, Clojure,<br>Erlang or languages from the PGAS family<br>* programming language support for heterogeneity<br>* programming language construct and features aimed at simplifying today's<br>software development, for example, transactional memory or deterministic<br>parallelism<br><br>Each article should clearly outline the problem to be addressed, the<br>solution or the findings, (at least) a proof of concept, and the options for<br>transferring the solution/findings into practice.<br><br>For more information about the special issue, contact the guest editors: <br>Laurence Tratt (<a href="mailto:laurie@tratt.net">laurie@tratt.net</a>)<br>Adam Welc (<a href="mailto:adamwwelc@gmail.com">adamwwelc@gmail.com</a>)<br><br><br>SUBMISSION GUIDELINES<br><br>Manuscripts must not exceed 4,700 words including figures and tables, which<br>count for 200 words each. Submissions in excess of these limits may be<br>rejected without refereeing. The articles we deem within the theme and scope<br>will be peer-reviewed and are subject to editing for magazine style, clarity,<br>organization, and space. We reserve the right to edit the title of all<br>submissions. Be sure to include the name of the theme or special issue you<br>are submitting for.<br><br>Articles should have a practical orientation and be written in a style<br>accessible to practitioners. Overly complex, purely research-oriented or<br>theoretical treatments are not appropriate. Articles should be novel. IEEE<br>Software does not republish material published previously in other venues,<br>including other periodicals and formal conference/workshop proceedings,<br>whether previous publication was in print or in electronic form.<br><br>For general author guidelines: <a href="http://www.computer.org/software/author.htm">http://www.computer.org/software/author.htm</a><br><br>For submission details: <a href="mailto:software@computer.org">software@computer.org</a><br><br>To submit an article: <a href="https://mc.manuscriptcentral.com/sw-cs">https://mc.manuscriptcentral.com/sw-cs</a><br>######################################################################</div>
<br></div></body></html>