The GPL v3 text says
The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work.

and I have no idea what that means.

There's an interesting FAQ entry, which contains the sentence

If the user uses your program to enter or convert his own data, the copyright on the output belongs to him, not you

Which seems to imply that if you write a compiler and license it under the GPLv3, the output still belongs to the user. Comforting.

Perl 6 - second systems done right

In reply to Re^5: Am I Allowed to Make a New Compiler/Language using Perl? by moritz
in thread Am I Allowed to Make a New Compiler/Language using Perl? by perl.j

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.