Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Right now there is no way to access the parse tree of the gcc from anywhere.

This is for my introspector.sf.net projects GCC patch and output.

The introspector itself could even stay under the GPL, but where would it get the semantically annotated parse trees from the gcc from?

There is no program database, no full symantic parser for emacs.

This would allow emacs and vim and other tools like DIA and VCG to access this data safely. That is what is is meant to do. A meta-data exchange.

It is not a general license for end user software, it is a license for program meta data. No one has any real tools for this right now in the c/c++ world. The perl::b modules are the only thing close, but there is no repository and browser for the output.

Please dont just jump to conclusions, I am not just proposing another license to propose another license. You cannot use any of the MSDN data for generation of free software tools. You cannot use the shared source from microsoft in a GPL program.<> This license is limited to GPLed software for the first phase and there is enough out there that would benefit from this program.

If the implications of the license are understood we can always expand it.

Please understand the limited scope of my license before shooting me!

mike


In reply to Re: Errr.. no.. by mdupont
in thread OT: A Modest Proposal for a GNU infrastructure license RGPL by mdupont

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others meditating upon the Monastery: (5)
As of 2024-04-24 22:42 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found