Hi,
John and I worked a bit together and updated the following parser:
- Delphi
- C# (supports version 6.0)
- JavaScript
As you know, SmaCC is now in the Moose distribution, and it comes with detailed abstract syntax trees. This offers new opportunities for the kinds of analyses we can provide.
Cheers,
Doru
--
www.tudorgirba.comwww.feenk.com
"There are no old things, there are only old ways of looking at them."
Hello,
I would like to report some random segfaults happing during the build of the Moose 6.1 image (based on Pharo 6).
Please find attached the latest failing stack trace.
Here are the 2 jobs that fails:
https://ci.inria.fr/moose/job/moose-6.1/345/consolehttps://ci.inria.fr/moose/job/moose-6.1/347/console
It seems that they are not failing for the same reason.
Maybe because the job is not using the latest VM? :
pharo VM version: 5.0 #1 Tue Jun 21 12:37:33 CEST 2016 gcc 4.6.3 [Production Spur ITHB VM]
Built from: CoInterpreter VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016
With: StackToRegisterMappingCogit VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016
Revision: https://github.com/pharo-project/pharo-vm.git Commit: 9638b0190a9fc01479bfb752becd96edfd253c8c Date: 2016-06-21 12:29:26 +0200 By: GitHub <noreply(a)github.com> Jenkins build #594
Build host: Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux
plugin path: /builds/workspace/moose-6.1/pharo-vm/ [default: /builds/workspace/moose-6.1/pharo-vm/]
Thanks in advance
Cheers,
Vincent
!!!*************************************************************************************
"Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"
Hi,
I am happy to announce the availability of PetitParser2, a wonderful redesign of the original PetitParser developed by Jan Kurš.
https://github.com/kursjan/petitparser2
Highlights:
- it introduces the compiler facility that speeds up parsers by a factor of ~2-5x
- it introduces the possibility of parsing streams without having them in memory
- it comes with a new structure internally that makes it more flexible
- it introduces asPParser (not a typo) to be able to have the new version working in parallel with the classic asParser
The version is already present in the latest Moose 6.1 in parallel with PetitParser. Also, several of the parsers that are shipping with PetitParser were already copied to PetitParser2 as well.
You can find more details here:
http://www.humane-assessment.com/blog/introducing-petitparser2/
Some more documentation will follow.
I think Jan did a wonderful job and the result is quite exciting. Please take a look and let us know what you think.
Cheers,
Doru
--
www.tudorgirba.comwww.feenk.com
"What we can governs what we wish."
Hi doru
If I have a model "model1" mse or database it will have internal names/id
then I have a delta or even another model
and loading it I will need to do a mapping between in memory objects of
the model 1
So you propose to remove all the entities related to entities in Model2
from model1 and to load load model2
but to do so you need to know that id:xxx in Model2 corresponds to Class
A in Model
My impression is that we should really have a uniqueName for any entity.
Stef
Hi,
I just wanted to know why the today Moose 6.1 jenkins jobs are failing : https://ci.inria.fr/moose/job/moose-6.1
It seems that someone changed the configuration to load iceberg :
./pharo $JOB_NAME.image eval "Metacello new \
baseline: 'Iceberg'; \
repository: 'github://npasserini/iceberg'; \
load. \
IceRepository defaultBackendType: IceLibgitLocalRepository. \
Smalltalk snapshot: true andQuit: true."
What is the status ?
Cheers,
Vincent
!!!*************************************************************************************
"Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"
Hi,
has anybody done anything with bug analysis in Pharo? I know that the most common approach is to see in which version an issue was closed and what code was changed and when was that code introduced and as the result you have lifespans of bugs.
Other suggestions are also welcome :)
Uko
----- Forwarded message -----
Hi,
Is it possible to configure the position of the GTDebugger panes to the previous version:
( http://humane-assessment.com/pierfiles/9e/kmq3rz0d783ks2m12lot6qg34ow8kd/gt… )
With the variables pane being a bit taller.
I remember that some people didn’t like this layout, that’s why I am asking whether it can be configured (for people that want to use this layout).
Thanks,
Peter
Hi,
I am playing a bit with RTMondrian and I cannot seem to be able to connect nested nodes. I am trying this:
view := RTMondrian new.
view nodes: (1 to: 2) forEach: [ :each |
view node: each * 10 ].
view edges source: {10->20} connectFrom: #key to: #value.
view
Given the advanced time, it might well be that I am missing something obvious. Or is it a regression?
Cheers,
Doru
--
www.tudorgirba.comwww.feenk.com
"We are all great at making mistakes."
