_st.js in directory 'support'?

> Hello
>
> the file
>
> contains
>
> define("amber_vm/_st", ["./boot"], function (boot) {
>      return boot._st;
> });
>
>
>
> It defines a module 'amber_vm/_st' and gives back the result of the
> module boot.js

>
>
> H. Hirzel wrote:
>> Hello
>>
>> the file
>>
>> contains
>>
>> define("amber_vm/_st", ["./boot"], function (boot) {
>>      return boot._st;
>> });
>>
>>
>>
>> It defines a module 'amber_vm/_st' and gives back the result of the
>> module boot.js
>
> Gives back its field '_st', to be precise.
>
>> What does _st stand for?
>
> Ask Nico why he chose that title. This is function used all over the
> compiled amber code that takes a value and returns proper receiver (null
> -> nil, plain JS object -> wrapped JS object, otherwise unchanged). In
> one of the recent issues I proposed to change it from _st to simple $,
> since it is used very often.
>
> The name of the module just mimicked the name of the variable. It can be
> changed, of course.
>
>> Kind regards
>>
>> Hannes
>
> Herby
>
> --
> You received this message because you are subscribed to the Google Groups
> "amber-lang" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [hidden email].
> For more options, visit https://groups.google.com/groups/opt_out.
>

> define("amber_core/Canvas",
>          ["amber_vm/smalltalk",   // list of modules on which are
> necessary for Canvas
>          "amber_vm/nil",
>          "amber_vm/_st",
>          "amber_core/Kernel-Objects",
>          "amber_core/Kernel-Infrastructure",
>          "amber_core/Kernel-Methods",
>          "amber_core/Kernel-Collections"],
>          function(smalltalk,nil,_st){                         // the
> canvas construction function
>                        smalltalk.addPackage('Canvas');
>          ......
>          }
>
>
> Is _st the "virtual machine"?

>
>
> H. Hirzel wrote:
>> define("amber_core/Canvas",
>>          ["amber_vm/smalltalk",   // list of modules on which are
>> necessary for Canvas
>>          "amber_vm/nil",
>>          "amber_vm/_st",
>>          "amber_core/Kernel-Objects",
>>          "amber_core/Kernel-Infrastructure",
>>          "amber_core/Kernel-Methods",
>>          "amber_core/Kernel-Collections"],
>>          function(smalltalk,nil,_st){                         // the
>> canvas construction function
>>                        smalltalk.addPackage('Canvas');
>>          ......
>>          }
>>
>>
>> Is _st the "virtual machine"?
>
> ???
> What did I do wrong in my previous explanation (really, I want to know)?
> I though I explained clearly that it is a function that transforms any value
> into proper amber receiver... :-/

>> And the definition of the module 'nil' is similar
>>
>> define("amber_vm/nil", ["./boot"], function (boot) {
>>      return boot.nil;
>> });
>
> Yes, it's the 'nil'.
>
>> What is the function of having this nil modu
> le?
>
> The important thing is the
>>          function(smalltalk,nil,_st){                         // the
>> canvas construction function
> which you cited before. Arguments to this function are filled from the
> modules listed before it. So "amber_vm/smalltalk" module export (that is
> return value) becomes 'smalltalk', "amber_vm/nil" export becomes 'nil' etc.
>
> Of course, similarly in
>> define("amber_vm/nil", ["./boot"], function (boot) {
>>      return boot.nil;
>> });
> the export of "./boot" goes to boot argument.

> On 9/6/13, Herby Vojčík<[hidden email]>  wrote:
>>
>> H. Hirzel wrote:
>>> define("amber_core/Canvas",
>>>           ["amber_vm/smalltalk",   // list of modules on which are
>>> necessary for Canvas
>>>           "amber_vm/nil",
>>>           "amber_vm/_st",
>>>           "amber_core/Kernel-Objects",
>>>           "amber_core/Kernel-Infrastructure",
>>>           "amber_core/Kernel-Methods",
>>>           "amber_core/Kernel-Collections"],
>>>           function(smalltalk,nil,_st){                         // the
>>> canvas construction function
>>>                         smalltalk.addPackage('Canvas');
>>>           ......
>>>           }
>>>
>>>
>>> Is _st the "virtual machine"?
>> ???
>> What did I do wrong in my previous explanation (really, I want to know)?
>> I though I explained clearly that it is a function that transforms any value
>> into proper amber receiver... :-/
>
> Extending what you wrote slightly,
> I now understand.
>
>
> "_st points to a function used all over the compiled amber code that
> takes any value (JavaScript or Smalltalk) and returns proper Amber
> Smalltalk receivers.
>
> null ->  nil,
> plain JS object ->  wrapped JS object,
> otherwise unchanged)."
>
> Correct?
>
> If yes, may I ask you to include this as a comment to _st.js ?
>
> This will enhance the code reading experience when I come back to this
> issue in three months because by then I probably will have forgotten.
>
> I can do a pull request, if you like.

> On 9/6/13, Herby Vojčík <[hidden email]> wrote:
>>
>>
>> H. Hirzel wrote:
>>> define("amber_core/Canvas",
>>>          ["amber_vm/smalltalk",   // list of modules on which are
>>> necessary for Canvas
>>>          "amber_vm/nil",
>>>          "amber_vm/_st",
>>>          "amber_core/Kernel-Objects",
>>>          "amber_core/Kernel-Infrastructure",
>>>          "amber_core/Kernel-Methods",
>>>          "amber_core/Kernel-Collections"],
>>>          function(smalltalk,nil,_st){                         // the
>>> canvas construction function
>>>                        smalltalk.addPackage('Canvas');
>>>          ......
>>>          }
>>>
>>>
>>> Is _st the "virtual machine"?
>>
>> ???
>> What did I do wrong in my previous explanation (really, I want to know)?
>> I though I explained clearly that it is a function that transforms any value
>> into proper amber receiver... :-/
>
> Extending what you wrote slightly,
> I now understand.
>
>
> "_st points to a function used all over the compiled amber code that
> takes any value (JavaScript or Smalltalk) and returns proper Amber
> Smalltalk receivers.
>
> null -> nil,
> plain JS object -> wrapped JS object,
> otherwise unchanged)."
>
> Correct?
>
> If yes, may I ask you to include this as a comment to _st.js ?
>
> This will enhance the code reading experience when I come back to this
> issue in three months because by then I probably will have forgotten.
>
> I can do a pull request, if you like.

>
>>> And the definition of the module 'nil' is similar
>>>
>>> define("amber_vm/nil", ["./boot"], function (boot) {
>>>      return boot.nil;
>>> });
>>
>> Yes, it's the 'nil'.
>>
>>> What is the function of having this nil modu
>> le?
>>
>> The important thing is the
>>>          function(smalltalk,nil,_st){                         // the
>>> canvas construction function
>> which you cited before. Arguments to this function are filled from the
>> modules listed before it. So "amber_vm/smalltalk" module export (that is
>> return value) becomes 'smalltalk', "amber_vm/nil" export becomes 'nil' etc.
>>
>> Of course, similarly in
>>> define("amber_vm/nil", ["./boot"], function (boot) {
>>>      return boot.nil;
>>> });
>> the export of "./boot" goes to boot argument.
>
> Thank you for this confirmation. In the meantime (since last Saturday)
> I learned enough of require.js to understand constructs like this
>
> define(moduleName, dependencyArray, moduleConstructionFunction)
>
> as well as it's simplifications as
>
> define(moduleName, moduleConstructionFunction)  // no dependencies
>
> and
>
> define(dependencyArray, moduleConstructionFunction)  // no name
>
> or even
>
> define(moduleConstructionFunction)  // no name, no dependencies
>
> see requirejs code
>     define = function (name, deps, callback)
> and then how the arguments are evaluated.
>
> What I am now aiming at is understanding the amber module hierarchy so
> that I can adapt it to my own needs.
>
> Thank you again, Herby,  for your prompt answer.
>
> --Hannes
>
> --
> You received this message because you are subscribed to the Google Groups "amber-lang" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> For more options, visit https://groups.google.com/groups/opt_out.