harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Spark Shen" <smallsmallor...@gmail.com>
Subject Re: [OT] new tools for Harmony
Date Thu, 25 Oct 2007 10:59:13 GMT
Anyhow, I think we are assured that we can use the grammer file and the
generated parser contributed by rigis.

2007/10/25, Alexei Fedotov <alexei.fedotov@gmail.com>:
>
> Spark,
> I pay attention to things created by my imagination behind the words,
> and this is what I call paranoia. :-)
>
> The Sun is no longer mentioned as JavaCC author [1]. This means that
> people around JavaCC are very flexible when talk about copyright. They
> might be no less flexible when stated these "free" and "caretaker"
> rights on the web page.
>
> In other words, I don't know if Sun really thinks that this tool is
> free. The truth is that is written on some web page with is not
> affiliated with Sun.
>
> [1] https://javacc.dev.java.net/
>
>
> On 10/25/07, Spark Shen <smallsmallorgan@gmail.com> wrote:
> > Thanks Alexei, for the information.
> >
> > I looked into the link, and noticed a paragraph:
> > <cite>
> > JavaCC is free. You can download it and use it in most situations at no
> > cost. The files generated by JavaCC are yours which you use at your own
> > risk. Sun and Metamata do not place any restrictions on what you can do
> with
> > the generated files.
> > </cite>
> >
> > According to these sentences, IMHO, whether to move or even remove the
> 'Do
> > not move' instructions is at our choice. But if it is required for some
> > technical reasons, for example, a tool will utilize that line, then it
> is
> > better be kept.
> >
> > 2007/10/24, Alexei Fedotov <alexei.fedotov@gmail.com>:
> > >
> > > Hello,
> > > I don't fully understand IP issues around javacc:
> > >
> > >    * The tool was initially developed by Sreeni while working for Sun.
> > >    * Then Sreeni left the company and created Metamata, which worked
> > > as caretaker for the tool and had a different license [2] than now.
> > >
> > > May be we should not be paranoid about it, but it worth to be
> mentioned.
> > > [1] http://www.cs.purdue.edu/homes/hosking/352/javaccdocs/usage.html
> > >
> > >
> > >
> > > On 10/24/07, Tim Ellison <t.p.ellison@gmail.com> wrote:
> > > > Regis wrote:
> > > > > Tim Ellison wrote:
> > > > >> Regis wrote:
> > > > >>> JavaCC is BSD licensed, it convert grammar file to java file,
> and
> > > > >>> according to it's FAQ[2], the java files produced by javacc
> > > > >>> can be used in any way.
> > > > >>>
> > > > >>> And javacc created java files with first line like this:
> > > > >>> "/* Generated By:JavaCC: Do not edit this line.
> FilterParser.java*/"
> > > > >>>
> > > > >>> Is it acceptable?
> > > > >>
> > > > >> Yep.  Please ensure that you also contribute the grammar files
> that
> > > you
> > > > >> write as input to javacc.  Both the grammar files and the
> resulting
> > > java
> > > > >> files should have the ASF standard block comments at the top
and
> be
> > > > >> checked into SVN.  It's probably a good idea to also keep the
'Do
> not
> > > > >> edit' instruction just so people know.
> > > > >>
> > > > > So we must move the 'Do not edit' instruction below the ASF
> standard
> > > block
> > > > > comments.
> > > >
> > > > It is not strictly necessary for the ASF comment to be the very
> first
> > > > thing in the file, but given that it is first by convention I would
> say
> > > > you should move the instruction below if it does not require a great
> > > effort.
> > > >
> > > > > And I think we should add a additional 'README' file, give some
> > > > > instruments about
> > > > > how to use the grammar files and generated source files.
> > > >
> > > > Yes, instructions to make the process reproducible are important.
> > > >
> > > > Thanks,
> > > > Tim
> > > >
> > >
> > >
> > > --
> > > With best regards,
> > > Alexei,
> > > ESSD, Intel
> > >
> >
> >
> >
> > --
> > Spark Shen
> > China Software Development Lab, IBM
> >
>
>
> --
> With best regards,
> Alexei,
> ESSD, Intel
>



-- 
Spark Shen
China Software Development Lab, IBM

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message