Devoted to the advancement of the Perl languages through discussion and code
Showing 4 of 4 projects. Click any project card for scope, mentors, and proposal studio.
Mentors: Student: Madeleine Goebel
<p>This project will add the capacity for Perl 6 to produce and execute self-contained binaries on Windows, Linux, and MacOS. I will start with an executable binary for a basic Hello World program, and incrementally add support for linking to shared system and user libraries. Time permitting, I will work with my mentors to enable support and/or work arounds to enable linking to C and other languages.</p> <p>My approach will be similar to how the .NET Core creates self-contained and framework dependent deployment binaries. I have chosen this as a model as it has proven capable of running on Linux, Windows, and MacOS systems. While my work may focus initially on either Windows and the Portable Executable (PE) or Linux and Executable and Linkable Format (ELF), this approach will hopefully ensure a path forward that will eventually be capable of producing executable binaries on all popular modern operating systems.</p> <p>The basic method which the .NET Core uses to create executable binaries is by creating a manifest of information in the operating system dependent executable binary format which is linked to .NET’s runtime library, and handed to a .NET “main” function which executes the user program.</p>
Mentors: Student: Joel Dale Schüller
<p>Improving the p6doc command line tool.</p>
Mentors: Student: Zhongnian Tao
<p>Develop encoding and decoding of GB2312 and GB18030 (simplified Chinese) for perl6.</p>
Mentors: Student: Antonio Gámiz Delgado
<p>Currently, pod6 files are processed by various scripts and modules (<code>htmlify.p6</code>, <code>Pod::To::HTML</code>, <code>Pod::To::BigPage</code>,...), that has repeated functionality, low level of testing, tight coupling between presentation rendering and source data. Even pod6 files are compiled several times.</p> <p>So, what I intend to do to change this? I have three objectives:</p> <ul> <li>Improve the stability of the system facing changes without provoking undesirable side effects.</li> <li>Speed up the build process to be able to make changes faster.</li> <li>Put together a lot of work in the docs done by several contributors during the last few years.</li> </ul>