Analyzing JavaScript
Locked
 
|
Hi!
We are currently trying to analyze JavaScript code in Moose. We have a working parser to generate .mse files. The parser extract for each JavaScript function its position in the source code, its amount of lines of code, incoming and outgoing invocations. We also have the nesting between functions. How can we represent this in Famix? A famix function can have a parent scope, but a parent scope can either be a package or a namespace, and not a function. Any hint ? Another question. How can we link the source code to the famix model? Help appreciated Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
At Synectique, we typically introduce new famix entities nicolas On 05/03/2013 12:39 AM, Alexandre Bergel wrote: > Hi! > > We are currently trying to analyze JavaScript code in Moose. We have a working parser to generate .mse files. The parser extract for each JavaScript function its position in the source code, its amount of lines of code, incoming and outgoing invocations. > We also have the nesting between functions. How can we represent this in Famix? A famix function can have a parent scope, but a parent scope can either be a package or a namespace, and not a function. Any hint ? > > Another question. How can we link the source code to the famix model? > > Help appreciated > > Cheers, > Alexandre > -- Nicolas Anquetil -- RMod research team (Inria) _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
In reply to this post by abergel
Hi,
We should promote parentScope to be container in FAMIXFunction. As for attaching the source anchor, take a look at FAMIXSourceAnchor and its subclasses. You should also take care of setting the language for your entities. For this, take a look at FAMIXSourceLanguage and its subclasses. And a question: is the parser available as open-source? Cheers, Doru On May 3, 2013, at 12:39 AM, Alexandre Bergel <[hidden email]> wrote: > Hi! > > We are currently trying to analyze JavaScript code in Moose. We have a working parser to generate .mse files. The parser extract for each JavaScript function its position in the source code, its amount of lines of code, incoming and outgoing invocations. > We also have the nesting between functions. How can we represent this in Famix? A famix function can have a parent scope, but a parent scope can either be a package or a namespace, and not a function. Any hint ? > > Another question. How can we link the source code to the famix model? > > Help appreciated > > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "Every now and then stop and ask yourself if the war you're fighting is the right one." _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
In reply to this post by Nicolas Anquetil
Ok, we will probably do so
Alexandre On May 3, 2013, at 3:16 AM, Nicolas Anquetil <[hidden email]> wrote: > > At Synectique, we typically introduce new famix entities > > nicolas > > On 05/03/2013 12:39 AM, Alexandre Bergel wrote: >> Hi! >> >> We are currently trying to analyze JavaScript code in Moose. We have a working parser to generate .mse files. The parser extract for each JavaScript function its position in the source code, its amount of lines of code, incoming and outgoing invocations. >> We also have the nesting between functions. How can we represent this in Famix? A famix function can have a parent scope, but a parent scope can either be a package or a namespace, and not a function. Any hint ? >> >> Another question. How can we link the source code to the famix model? >> >> Help appreciated >> >> Cheers, >> Alexandre >> > > -- > Nicolas Anquetil -- RMod research team (Inria) > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
In reply to this post by Tudor Girba-2
> We should promote parentScope to be container in FAMIXFunction.
> > As for attaching the source anchor, take a look at FAMIXSourceAnchor and its subclasses. > > You should also take care of setting the language for your entities. For this, take a look at FAMIXSourceLanguage and its subclasses. Ok > And a question: is the parser available as open-source? Sure. It is in its stabilization phase. We will soon release it. Alexandre > > > On May 3, 2013, at 12:39 AM, Alexandre Bergel <[hidden email]> wrote: > >> Hi! >> >> We are currently trying to analyze JavaScript code in Moose. We have a working parser to generate .mse files. The parser extract for each JavaScript function its position in the source code, its amount of lines of code, incoming and outgoing invocations. >> We also have the nesting between functions. How can we represent this in Famix? A famix function can have a parent scope, but a parent scope can either be a package or a namespace, and not a function. Any hint ? >> >> Another question. How can we link the source code to the famix model? >> >> Help appreciated >> >> Cheers, >> Alexandre >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > www.tudorgirba.com > > "Every now and then stop and ask yourself if the war you're fighting is the right one." > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
In reply to this post by Tudor Girba-2
Done in Famix-Core-AlexandreBergel.215
Alexandre On May 3, 2013, at 10:37 AM, Tudor Girba <[hidden email]> wrote: > Hi, > > We should promote parentScope to be container in FAMIXFunction. > > As for attaching the source anchor, take a look at FAMIXSourceAnchor and its subclasses. > > You should also take care of setting the language for your entities. For this, take a look at FAMIXSourceLanguage and its subclasses. > > And a question: is the parser available as open-source? > > Cheers, > Doru > > > On May 3, 2013, at 12:39 AM, Alexandre Bergel <[hidden email]> wrote: > >> Hi! >> >> We are currently trying to analyze JavaScript code in Moose. We have a working parser to generate .mse files. The parser extract for each JavaScript function its position in the source code, its amount of lines of code, incoming and outgoing invocations. >> We also have the nesting between functions. How can we represent this in Famix? A famix function can have a parent scope, but a parent scope can either be a package or a namespace, and not a function. Any hint ? >> >> Another question. How can we link the source code to the famix model? >> >> Help appreciated >> >> Cheers, >> Alexandre >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > www.tudorgirba.com > > "Every now and then stop and ask yourself if the war you're fighting is the right one." > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
What is done? :) Doru On Thu, Jun 6, 2013 at 9:13 PM, Alexandre Bergel <[hidden email]> wrote: Done in Famix-Core-AlexandreBergel.215 "Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
Promote parentScope to be container in FAMIXFunction
Sorry if it was not clear. Maybe you can have a look at Famix-Core-AlexandreBergel.215 to double check everything is fine Alexandre On Jun 6, 2013, at 3:43 PM, Tudor Girba <[hidden email]> wrote: > What is done? :) > > Doru > > > On Thu, Jun 6, 2013 at 9:13 PM, Alexandre Bergel <[hidden email]> wrote: > Done in Famix-Core-AlexandreBergel.215 > > Alexandre > > > On May 3, 2013, at 10:37 AM, Tudor Girba <[hidden email]> wrote: > > > Hi, > > > > We should promote parentScope to be container in FAMIXFunction. > > > > As for attaching the source anchor, take a look at FAMIXSourceAnchor and its subclasses. > > > > You should also take care of setting the language for your entities. For this, take a look at FAMIXSourceLanguage and its subclasses. > > > > And a question: is the parser available as open-source? > > > > Cheers, > > Doru > > > > > > On May 3, 2013, at 12:39 AM, Alexandre Bergel <[hidden email]> wrote: > > > >> Hi! > >> > >> We are currently trying to analyze JavaScript code in Moose. We have a working parser to generate .mse files. The parser extract for each JavaScript function its position in the source code, its amount of lines of code, incoming and outgoing invocations. > >> We also have the nesting between functions. How can we represent this in Famix? A famix function can have a parent scope, but a parent scope can either be a package or a namespace, and not a function. Any hint ? > >> > >> Another question. How can we link the source code to the famix model? > >> > >> Help appreciated > >> > >> Cheers, > >> Alexandre > >> > >> -- > >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >> Alexandre Bergel http://www.bergel.eu > >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >> > >> > >> > >> > >> _______________________________________________ > >> Moose-dev mailing list > >> [hidden email] > >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > -- > > www.tudorgirba.com > > > > "Every now and then stop and ask yourself if the war you're fighting is the right one." > > > > > > > > > > _______________________________________________ > > Moose-dev mailing list > > [hidden email] > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
Ok. Will do. Doru On Thu, Jun 6, 2013 at 9:52 PM, Alexandre Bergel <[hidden email]> wrote:
"Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
«
Return to Moose
|
1 view|%1 views
| Free forum by Nabble | Edit this page |