Moose-dev February 2014

moose-dev@list.inf.unibe.ch

32 participants
93 discussions

by Stephan Eggermont

>As far as I got the time to see, those implementations have full ASTs. The Java one has classes with instVars, but no methods at all… Stephan

10 years, 10 months

Jenkins build became unstable: moose-5.0 #685

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-5.0/685/>

10 years, 10 months

Re: SmaCC status?

by Stephan Eggermont

I assume you want spec for: #'pharo3.x' version: '2.0.3' instead of 203. I’m blocked on the use of git at the moment (see pharo list) Stephan

10 years, 10 months

Things I'm missing in the Glamorous Debugger

by Friedrich Dominicus

Ok here are the things I used to have but am missin in the Glamourous debugger - Inspection of values (yes they are listed in the lower area) but there can be quite a few Variables in which I may or may not be interested. - there is simply no workspace available in the debugger. So just issuing a few commands simply does not do it. - I personally find the stepping symbols to small. They are not reall bad but kind of "strange" Regards Friedrich

10 years, 10 months

Hello

by Lorenzo Baracchi

Hello, I write this message only to introduce myself. I am Lorenzo Baracchi and currently I am working on my MSc thesis at the University of Lugano in the REVEAL research group. I might need to use MOOSE during my thesis, so I'll post any question here! Cheers Lorenzo

10 years, 10 months

SmaCC status?

by Stephan Eggermont

I was looking at SmaCC and noticed the latest version on Dolphin and VW seems to support GLR parsing. What would be needed to make that work on Pharo (3/Moose5)? What practical consequences might I expect if we replace a PetitParser based parser by a SmaCC one? Stephan

10 years, 10 months

Issue 1036 in moose-technology: Ctrl + S and Alt + S haven't the same behaviour

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1036 by v.blonde...(a)gmail.com: Ctrl + S and Alt + S haven't the same behaviour http://code.google.com/p/moose-technology/issues/detail?id=1036 Describe the problem: what do you get? what do you expect? To save the modified source code in the debugger under Pharo3.0, we can make Ctrl + S or Alt + S. But with the latest version of Moose5.0. Alt + S save the source and move the stack to the saved method. Ctrl + S only save the source. How to reproduce the problem: step by step if necessary Open a debugger, select an other method in the stack trace, modify it. Try to save with Ctrl + S and do it again with Alt + S. Additional information: platform, context which may impact the problem Windows 7 x64 and Linux Ubuntu x64 Please fill in the labels with the following information: * Type-Defect * Component-GTDebugger * Milestone-5.0 -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

10 years, 10 months

Build failed in Jenkins: moose-5.0 #676

by admin＠moosetechnology.org

10 years, 10 months

Jenkins build is back to stable : moose-5.0 #666

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-5.0/666/>

10 years, 10 months

Jenkins build became unstable: moose-5.0 #664

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-5.0/664/>

10 years, 10 months

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev February 2014