Enhanced Amber REPL

Yes, something like 'var not found' or 'q is undefined'. For any
undefined variable there are these trace messages.

And: How do I load and execute a script?

--Hannes

On 9/8/13, Markus Kahl <[hidden email]> wrote:
> Exatly what Thomas said. Perhaps we should have an appropriate error
> message (var not found or similar) instead of the trace when you just type
> q, though.
>
> Am Sonntag, 8. September 2013 01:54:15 UTC+1 schrieb Thomas Rake:
>>
>> Hello Hanes,
>>
>> The REPL quit command is  ':q' which works on my Window machine based on
>> the current master. Typing just q results in a Amber trace for the
>> undefined symbol q.
>>
>>
>>
>> On Saturday, September 7, 2013 1:51:05 AM UTC-4, Hannes wrote:
>>>
>>> Hello Markus
>>>
>>> With the current amber the q command in the REPL does not work properly.
>>>
>>>
>>> I start the REPL loop in MSWindows with
>>>
>>> C:\Users\User\Documents\projects>vendor\amber\bin\amber repl
>>>
>>> C:\Users\User\Documents\projects>vendor\amber\bin\amber repl
>>> Welcome to Amber version 0.12.0-pre (NodeJS 0.10.17).
>>> Type :q to exit.
>>>
>>> amber >> 1 + 1
>>> res1: Number = 2
>>>
>>> amber >> q
>>> a block (in nil)
>>> Repl >> processLine:
>>> Repl >> assignNewVariable:do:
>>> Repl >> parseAssignment:do:
>>> BlockClosure >> value:value:
>>> a block (in BlockClosure >> value:value:)
>>> Repl >> eval:on:
>>> Repl >> try:catch:
>>> BlockClosure >> value
>>> a block (in BlockClosure >> value)
>>> Compiler >> evaluateExpression:on:
>>> Compiler >> compileExpression:on:
>>> Compiler >> compileNode:
>>> InliningCodeGenerator >> compileNode:
>>> SemanticAnalyzer >> visit:
>>> MethodNode >> accept:
>>> SemanticAnalyzer >> visitMethodNode:
>>> SemanticAnalyzer >> visitMethodNode:
>>> SemanticAnalyzer >> visitNode:
>>> SemanticAnalyzer >> visitAll:
>>> Array >> collect:
>>> BlockClosure >> value:
>>> a block (in BlockClosure >> value:)
>>> SemanticAnalyzer >> visit:
>>> SequenceNode >> accept:
>>> SemanticAnalyzer >> visitSequenceNode:
>>> SemanticAnalyzer >> visitSequenceNode:
>>> SemanticAnalyzer >> visitNode:
>>> SemanticAnalyzer >> visitAll:
>>> Array >> collect:
>>> BlockClosure >> value:
>>> a block (in BlockClosure >> value:)
>>>  .......
>>>
>>> Regards
>>> Hannes
>>>
>>> On 6/24/13, Manfred Kröhnert <[hidden email]> wrote:
>>> > Hi Markus,
>>> >
>>> > On Mon, Jun 24, 2013 at 12:01 PM, Markus Kahl <[hidden email]>
>>> wrote:
>>> >
>>> >> Hey,
>>> >>
>>> >> alright thanks, I've just created one.
>>> >>
>>> >
>>> > Great!
>>> >
>>> >
>>> >> The repl didn't understand 'quit' as far as I know. Also no sign of
>>> >> anything like it in the code.
>>> >>
>>> >
>>> > Okay, then I just remembered incorrectly.
>>> >
>>> >
>>> >> ~ Markus
>>> >>
>>> >
>>> > Keep going :-)
>>> > Manfred
>>> >
>>> >
>>> >
>>> >> Am Montag, 24. Juni 2013 09:27:39 UTC+1 schrieb Manfred Kröhnert:
>>> >>>
>>> >>> Hello Markus,
>>> >>>
>>> >>> don't hesitate to open a pull-request.
>>> >>> If there is something which needs some tweaking we will discuss it
>>> >>> there.
>>> >>> It is also great if you write a short summary of the changes there so
>>> >>>
>>> we
>>> >>> don't have to go through the commits to extract that information :-)
>>> >>>
>>> >>>
>>> >>> And for the coding style there is a wiki page mentioning the most
>>> >>> important things.
>>> >>>
>>> >>> Regarding ':q to quit'.
>>> >>> Didn't the REPL already understand the 'quit' message?
>>> >>>
>>> >>> Best regards,
>>> >>> Manfred
>>> >>> Am 23.06.2013 20:45 schrieb "Markus Kahl" <[hidden email]>:
>>> >>>
>>> >>>> Hey,
>>> >>>>
>>> >>>> I've enhanced the Amber REPL a little because I wanted to play
>>> around a
>>> >>>> bit (with access to node.js) and it was missing a couple of things
>>> I'm
>>> >>>> used
>>> >>>> to.
>>> >>>> Dunno how commonly used the REPL is, but do you think it'd make
>>> sense
>>> >>>> to
>>> >>>> create a pull request?
>>> >>>> This way perhaps other people could get a more useful REPL, too.
>>> >>>> Are there any coding standards I'd need to pay attention to?
>>> >>>> My Smalltalk style is quite possibly horrible.
>>> >>>>
>>> >>>>
>>> >>>> <
>>> https://lh3.googleusercontent.com/-lZCW70DDb4I/UcdBSVbifVI/AAAAAAAAAFA/gNgFWmL8c44/s1600/amber-repl.png>
>>>
>>>
>>> >>>>
>>> >>>> A little picture demonstrating some of the new REPL features
>>> >>>>
>>> >>>> Additionally to the features shown in the screenshot (mainly
>>> variables)
>>> >>>> I've also implemented Ctrl+L to clear the screen.
>>> >>>>
>>> >>>> ~ Markus
>>> >>>>
>>> >>>>
>>> >
>>> > --
>>> > 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.
>>> >
>>> >
>>> >
>>>
>>
>
> --
> 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.
>

--
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.

Yes, printing an error message instead of showing a stacktrace sounds like a good addition.

As of now it is not possible to load and execute external scripts.

However, it should not be too hard to support this since one would have to do the same steps amberc does without writing the file back out again.

But Writing Packages to disk sounds like a nice addition, too.

Best,

Manfred

On Mon, Sep 9, 2013 at 6:14 AM, H. Hirzel <[hidden email]> wrote:

Yes, something like 'var not found' or 'q is undefined'. For any
undefined variable there are these trace messages.

And: How do I load and execute a script?

--Hannes

On 9/8/13, Markus Kahl <[hidden email]> wrote:
> Exatly what Thomas said. Perhaps we should have an appropriate error
> message (var not found or similar) instead of the trace when you just type
> q, though.
>
> Am Sonntag, 8. September 2013 01:54:15 UTC+1 schrieb Thomas Rake:
>>
>> Hello Hanes,
>>
>> The REPL quit command is  ':q' which works on my Window machine based on
>> the current master. Typing just q results in a Amber trace for the
>> undefined symbol q.
>>
>>
>>
>> On Saturday, September 7, 2013 1:51:05 AM UTC-4, Hannes wrote:
>>>
>>> Hello Markus
>>>
>>> With the current amber the q command in the REPL does not work properly.
>>>
>>>
>>> I start the REPL loop in MSWindows with
>>>
>>> C:\Users\User\Documents\projects>vendor\amber\bin\amber repl
>>>
>>> C:\Users\User\Documents\projects>vendor\amber\bin\amber repl
>>> Welcome to Amber version 0.12.0-pre (NodeJS 0.10.17).
>>> Type :q to exit.
>>>
>>> amber >> 1 + 1
>>> res1: Number = 2
>>>
>>> amber >> q
>>> a block (in nil)
>>> Repl >> processLine:
>>> Repl >> assignNewVariable:do:
>>> Repl >> parseAssignment:do:
>>> BlockClosure >> value:value:
>>> a block (in BlockClosure >> value:value:)
>>> Repl >> eval:on:
>>> Repl >> try:catch:
>>> BlockClosure >> value
>>> a block (in BlockClosure >> value)
>>> Compiler >> evaluateExpression:on:
>>> Compiler >> compileExpression:on:
>>> Compiler >> compileNode:
>>> InliningCodeGenerator >> compileNode:
>>> SemanticAnalyzer >> visit:
>>> MethodNode >> accept:
>>> SemanticAnalyzer >> visitMethodNode:
>>> SemanticAnalyzer >> visitMethodNode:
>>> SemanticAnalyzer >> visitNode:
>>> SemanticAnalyzer >> visitAll:
>>> Array >> collect:
>>> BlockClosure >> value:
>>> a block (in BlockClosure >> value:)
>>> SemanticAnalyzer >> visit:
>>> SequenceNode >> accept:
>>> SemanticAnalyzer >> visitSequenceNode:
>>> SemanticAnalyzer >> visitSequenceNode:
>>> SemanticAnalyzer >> visitNode:
>>> SemanticAnalyzer >> visitAll:
>>> Array >> collect:
>>> BlockClosure >> value:
>>> a block (in BlockClosure >> value:)
>>>  .......
>>>
>>> Regards
>>> Hannes
>>>
>>> On 6/24/13, Manfred Kröhnert <[hidden email]> wrote:
>>> > Hi Markus,
>>> >
>>> > On Mon, Jun 24, 2013 at 12:01 PM, Markus Kahl <[hidden email]>
>>> wrote:
>>> >
>>> >> Hey,
>>> >>
>>> >> alright thanks, I've just created one.
>>> >>
>>> >
>>> > Great!
>>> >
>>> >
>>> >> The repl didn't understand 'quit' as far as I know. Also no sign of
>>> >> anything like it in the code.
>>> >>
>>> >
>>> > Okay, then I just remembered incorrectly.
>>> >
>>> >
>>> >> ~ Markus
>>> >>
>>> >
>>> > Keep going :-)
>>> > Manfred
>>> >
>>> >
>>> >
>>> >> Am Montag, 24. Juni 2013 09:27:39 UTC+1 schrieb Manfred Kröhnert:
>>> >>>
>>> >>> Hello Markus,
>>> >>>
>>> >>> don't hesitate to open a pull-request.
>>> >>> If there is something which needs some tweaking we will discuss it
>>> >>> there.
>>> >>> It is also great if you write a short summary of the changes there so
>>> >>>
>>> we
>>> >>> don't have to go through the commits to extract that information :-)
>>> >>>
>>> >>>
>>> >>> And for the coding style there is a wiki page mentioning the most
>>> >>> important things.
>>> >>>
>>> >>> Regarding ':q to quit'.
>>> >>> Didn't the REPL already understand the 'quit' message?
>>> >>>
>>> >>> Best regards,
>>> >>> Manfred
>>> >>> Am 23.06.2013 20:45 schrieb "Markus Kahl" <[hidden email]>:
>>> >>>
>>> >>>> Hey,
>>> >>>>
>>> >>>> I've enhanced the Amber REPL a little because I wanted to play
>>> around a
>>> >>>> bit (with access to node.js) and it was missing a couple of things
>>> I'm
>>> >>>> used
>>> >>>> to.
>>> >>>> Dunno how commonly used the REPL is, but do you think it'd make
>>> sense
>>> >>>> to
>>> >>>> create a pull request?
>>> >>>> This way perhaps other people could get a more useful REPL, too.
>>> >>>> Are there any coding standards I'd need to pay attention to?
>>> >>>> My Smalltalk style is quite possibly horrible.
>>> >>>>
>>> >>>>
>>> >>>> <
>>> https://lh3.googleusercontent.com/-lZCW70DDb4I/UcdBSVbifVI/AAAAAAAAAFA/gNgFWmL8c44/s1600/amber-repl.png>
>>>
>>>
>>> >>>>
>>> >>>> A little picture demonstrating some of the new REPL features
>>> >>>>
>>> >>>> Additionally to the features shown in the screenshot (mainly
>>> variables)
>>> >>>> I've also implemented Ctrl+L to clear the screen.
>>> >>>>
>>> >>>> ~ Markus
>>> >>>>
>>> >>>>
>>> >
>>> > --
>>> > 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.
>>> >
>>> >
>>> >
>>>
>>
>
> --
> 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.
>

--
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.