14 Sep
2015
14 Sep
'15
11:49 a.m.
Hi,
I propose to change this:
MoosModel>>sourceLanguage: aSymbol
^sourceLanguage := aSymbol
by:
MoosModel>>sourceLanguage: aSourceLanguage
sourceLanguage := aSourceLanguage.
sourceLanguage mooseModel: self
So, that we don't have to remember to add manually the source language to
the model.
Is it ok to do this change?
usman
14 Sep
14 Sep
12:55 p.m.
Sounds good. But, if we add it to the MooseModel, then we will not need the
instance variable, because it will be added in the pool of entities.
Doru
On Mon, Sep 14, 2015 at 11:49 AM, Usman Bhatti <usman.bhatti(a)gmail.com>
wrote:
Hi,
I propose to change this:
MoosModel>>sourceLanguage: aSymbol
^sourceLanguage := aSymbol
by:
MoosModel>>sourceLanguage: aSourceLanguage
sourceLanguage := aSourceLanguage.
sourceLanguage mooseModel: self
So, that we don't have to remember to add manually the source language to
the model.
Is it ok to do this change?
usman
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every thing has its own flow"
1:28 p.m.
On Mon, Sep 14, 2015 at 12:55 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
Sounds good. But, if we add it to the MooseModel, then
we will not need
the instance variable, because it will be added in the pool of entities.
Agreed. That information is redundant and we can remove Instance variable.
So, the getter becomes
MooseModel>>sourceLanguage
<MSEProperty: #sourceLanguage type: #FAMIXSourceLanguage>
<MSEComment: 'Source of the Language to which the model corresponds'>
^ self
propertyNamed: name
ifAbsentPut: [ self allSourceLanguages detect: [ :each | each isAttached
not ] ifNone: [ FAMIXUnknownSourceLanguage new ] ]
I'll do this change.
Doru
On Mon, Sep 14, 2015 at 11:49 AM, Usman Bhatti <usman.bhatti(a)gmail.com>
wrote:
Hi,
I propose to change this:
MoosModel>>sourceLanguage: aSymbol
^sourceLanguage := aSymbol
by:
MoosModel>>sourceLanguage: aSourceLanguage
sourceLanguage := aSourceLanguage.
sourceLanguage mooseModel: self
So, that we don't have to remember to add manually the source language to
the model.
Is it ok to do this change?
usman
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
1:37 p.m.
On 14-09-15 13:28, Usman Bhatti wrote:
Agreed. That information is redundant and we can
remove Instance
variable. So, the getter becomes MooseModel>>sourceLanguage
<MSEProperty: #sourceLanguage type: #FAMIXSourceLanguage> <MSEComment:
'Source of the Language to which the model corresponds'> ^ self
propertyNamed: name ifAbsentPut: [ self allSourceLanguages detect: [
:each | each isAttached not ] ifNone: [ FAMIXUnknownSourceLanguage new
] ] I'll do this change.
In models with multiple languages, using the first found (detect:) can
be wrong.
If one would load a java model, one might start from a maven description.
Stephan
1:31 p.m.
On 14-09-15 11:49, Usman Bhatti wrote:
Hi,
I propose to change this:
MoosModel>>sourceLanguage: aSymbol
^sourceLanguage := aSymbol
by:
MoosModel>>sourceLanguage: aSourceLanguage
sourceLanguage := aSourceLanguage.
sourceLanguage mooseModel: self
So, that we don't have to remember to add manually the source language to
the model.
What is the MooseModel sourceLanguage? A model can have multiple languages.
Stephan
2 p.m.
On Mon, Sep 14, 2015 at 1:31 PM, stephan <stephan(a)stack.nl> wrote:
On 14-09-15 11:49, Usman Bhatti wrote:
I think a model can have only one principal language.
Then each FAMIXSourcedEntity have declared language other than the source
language of their container model.
Hi,
I propose to change this:
MoosModel>>sourceLanguage: aSymbol
^sourceLanguage := aSymbol
by:
MoosModel>>sourceLanguage: aSourceLanguage
sourceLanguage := aSourceLanguage.
sourceLanguage mooseModel: self
So, that we don't have to remember to add manually the source language to
the model.
What is the MooseModel sourceLanguage? A model can have multiple languages.
Stephan
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
3:22 p.m.
On 14-09-15 14:00, Usman Bhatti wrote:
On Mon, Sep 14, 2015 at 1:31 PM, stephan
<stephan(a)stack.nl> wrote:
What is the MooseModel sourceLanguage? A model can have multiple languages.
I think a model can have only one principal language.
Then each FAMIXSourcedEntity have declared language other than the source
language of their container model.
That might be somewhat arbitrary. What about a
php+sql+javascript+css+html application?
What do we use this for?
Stephan
4:09 p.m.
Multiple languages in the same model make sense if, say, you had F# and C#
since the runtimes are the same, and will share similarities. Ideally,
you'd be able to analyze relationships across the two languages. Same goes
for JavaScript, CoffeeScript, TypeScript, JSX (et al.).
However, I'm confused by the idea of putting, say, SQL and PHP into the
same model. Are there meaningful analyses that you can do with a
heterogeneous model like that?
On Mon, Sep 14, 2015 at 8:22 AM, stephan <stephan(a)stack.nl> wrote:
On 14-09-15 14:00, Usman Bhatti wrote:
On Mon, Sep 14, 2015 at 1:31 PM, stephan
<stephan(a)stack.nl> wrote:
What is the MooseModel sourceLanguage? A model can have multiple
languages.
I think a model can have only one principal language.
Then each FAMIXSourcedEntity have declared language other than the source
language of their container model.
That might be somewhat arbitrary. What about a
php+sql+javascript+css+html
application?
What do we use this for?
Stephan
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
11:56 p.m.
On 14/09/15 16:09, Floyd May wrote:
However, I'm confused by the idea of putting, say, SQL and PHP into
the same model. Are there meaningful analyses that you can do with a
heterogeneous model like that?
For systems that use the database as integration
layer
I don't know about an alternative. I agree that we don't
have many pre-build analyses for systems like that.
Stephan
15 Sep
15 Sep
9:21 a.m.
There certainly are analyses to be done with systems like these. That is
actually one of the powers of Moose that is allows you to build such
heterogeneous models.
Doru
On Mon, Sep 14, 2015 at 11:56 PM, Stephan Eggermont <stephan(a)stack.nl>
wrote:
On 14/09/15 16:09, Floyd May wrote:
--
www.tudorgirba.com
"Every thing has its own flow"
However, I'm confused by the idea of putting, say, SQL and PHP into the
same model. Are there meaningful analyses that you can do with a
heterogeneous model like that?
For systems that use the database as integration layer
I don't know about an alternative. I agree that we don't
have many pre-build analyses for systems like that.
Stephan
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
11:40 p.m.
Every SourcedEntity knows its language. The MooseModel>>sourceLanguage is a
fallback.
Doru
On Mon, Sep 14, 2015 at 3:22 PM, stephan <stephan(a)stack.nl> wrote:
On 14-09-15 14:00, Usman Bhatti wrote:
--
www.tudorgirba.com
"Every thing has its own flow"
On Mon, Sep 14, 2015 at 1:31 PM, stephan
<stephan(a)stack.nl> wrote:
What is the MooseModel sourceLanguage? A model can have multiple
languages.
I think a model can have only one principal language.
Then each FAMIXSourcedEntity have declared language other than the source
language of their container model.
That might be somewhat arbitrary. What about a
php+sql+javascript+css+html
application?
What do we use this for?
Stephan
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
14 Sep
14 Sep
3:15 p.m.
Shouldn’t an entity be aware of the language it written in? Why the model?
Alexandre
On Sep 14, 2015, at 6:49 AM, Usman Bhatti
<usman.bhatti(a)gmail.com> wrote:
Hi,
I propose to change this:
MoosModel>>sourceLanguage: aSymbol
^sourceLanguage := aSymbol
by:
MoosModel>>sourceLanguage: aSourceLanguage
sourceLanguage := aSourceLanguage.
sourceLanguage mooseModel: self
So, that we don't have to remember to add manually the source language to the model.
Is it ok to do this change?
usman
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
15 Sep
15 Sep
10:42 a.m.
On 14/09/2015 15:15, Alexandre Bergel wrote:
Shouldn’t an entity be aware of the language it
written in? Why the model?
by default, the language of an entity is the language of
the model.
Thus for single language project, you don't need to specify the
sourceLanguage for each and every entity.
For projects which multiple languages, one can either elect one language
as the default one (and set individually the language of all other
entities) or not set any default language (and set individually the
language of all entities)
nicolas
Alexandre
> On Sep 14, 2015, at 6:49 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote:
>
> Hi,
>
> I propose to change this:
>
> MoosModel>>sourceLanguage: aSymbol
> ^sourceLanguage := aSymbol
>
> by:
>
> MoosModel>>sourceLanguage: aSourceLanguage
> sourceLanguage := aSourceLanguage.
> sourceLanguage mooseModel: self
>
> So, that we don't have to remember to add manually the source language to the
model.
>
> Is it ok to do this change?
>
> usman
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
11:08 a.m.
On 15-09-15 10:42, Nicolas Anquetil wrote:
On 14/09/2015 15:15, Alexandre Bergel wrote:
Thank you, that makes sense. Then I propose to rename the instance
variable to defaultLanguage
with accessors (and add the explanation in a method comment)
Stephan
Shouldn’t an entity be aware of the language it
written in? Why the
model?
by default, the language of an entity is the language of the model.
Thus for single language project, you don't need to specify the
sourceLanguage for each and every entity.
For projects which multiple languages, one can either elect one
language as the default one (and set individually the language of all
other entities) or not set any default language (and set individually
the language of all entities) 
16 Sep
16 Sep
9:45 a.m.
+1
2015-09-15 11:08 GMT+02:00 stephan <stephan(a)stack.nl>nl>:
On 15-09-15 10:42, Nicolas Anquetil wrote:
On 14/09/2015 15:15, Alexandre Bergel wrote:
Thank you, that makes sense. Then I propose to rename the instance variable
to defaultLanguage
with accessors (and add the explanation in a method comment)
Stephan
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Shouldn’t an entity be aware of the language it written in? Why the
model?
by default, the language of an entity is the language of the model.
Thus for single language project, you don't need to specify the
sourceLanguage for each and every entity.
For projects which multiple languages, one can either elect one language
as the default one (and set individually the language of all other entities)
or not set any default language (and set individually the language of all
entities)
9:46 a.m.
+1 to rename the instance variable to defaultLanguage :)
2015-09-16 9:45 GMT+02:00 Fabrizio Perin <fabrizio.perin(a)gmail.com>om>:
+1
2015-09-15 11:08 GMT+02:00 stephan <stephan(a)stack.nl>nl>:
>
>
> On 15-09-15 10:42, Nicolas Anquetil wrote:
>>
>>
>> On 14/09/2015 15:15, Alexandre Bergel wrote:
>>>
>>> Shouldn’t an entity be aware of the language it written in? Why the
>>> model?
>>
>> by default, the language of an entity is the language of the model.
>> Thus for single language project, you don't need to specify the
>> sourceLanguage for each and every entity.
>>
>> For projects which multiple languages, one can either elect one language
>> as the default one (and set individually the language of all other entities)
>> or not set any default language (and set individually the language of all
>> entities)
>
>
> Thank you, that makes sense. Then I propose to rename the instance variable
> to defaultLanguage
> with accessors (and add the explanation in a method comment)
>
> Stephan
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
10:31 a.m.
makes sense to me to
nicolas
On 16/09/2015 09:46, Fabrizio Perin wrote:
+1 to rename the instance variable to defaultLanguage
:)
2015-09-16 9:45 GMT+02:00 Fabrizio Perin <fabrizio.perin(a)gmail.com>om>:
+1
2015-09-15 11:08 GMT+02:00 stephan <stephan(a)stack.nl>nl>:
>
> On 15-09-15 10:42, Nicolas Anquetil wrote:
>>
>> On 14/09/2015 15:15, Alexandre Bergel wrote:
>>> Shouldn’t an entity be aware of the language it written in? Why the
>>> model?
>> by default, the language of an entity is the language of the model.
>> Thus for single language project, you don't need to specify the
>> sourceLanguage for each and every entity.
>>
>> For projects which multiple languages, one can either elect one language
>> as the default one (and set individually the language of all other entities)
>> or not set any default language (and set individually the language of all
>> entities)
>
> Thank you, that makes sense. Then I propose to rename the instance variable
> to defaultLanguage
> with accessors (and add the explanation in a method comment)
>
> Stephan
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
3156
days inactive
3158
days old
16 comments
8 participants
participants (8)
-
Alexandre Bergel -
Fabrizio Perin -
Floyd May -
Nicolas Anquetil -
stephan -
Stephan Eggermont
-
Tudor Girba -
Usman Bhatti