Moose-dev March 2011

moose-dev@list.inf.unibe.ch

24 participants
119 discussions

Issue 537 in moose-technology: inFusion should export explicit sourceAnchor for Function

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 537 by tudor.gi...(a)gmail.com: inFusion should export explicit sourceAnchor for Function http://code.google.com/p/moose-technology/issues/detail?id=537 Currently, it exports sourceAnchor as a string like this: (FAMIX.Function (sourceAnchor 'path') ...) It should be (FAMIX.FileAnchor (id: 1) ...) (FAMIX.Function (sourceAnchor (ref: 1)))

12 years, 8 months

Issue 544 in moose-technology: inFusion should point the C++ source text to the implementation, not definition

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 544 by tudor.gi...(a)gmail.com: inFusion should point the C++ source text to the implementation, not definition http://code.google.com/p/moose-technology/issues/detail?id=544 Currently, the source anchor for a c/c++ class or methods points to the definition in the header. It should point to the implementation from the c/cpp file.

12 years, 8 months

Re: Issue 464 in moose-technology: Actions that open new browsers should go through Renderer

by moose-technology＠googlecode.com

Updates: Labels: -Milestone-4.2 Comment #1 on issue 464 by tudor.gi...(a)gmail.com: Actions that open new browsers should go through Renderer http://code.google.com/p/moose-technology/issues/detail?id=464 (No comment was entered for this change.)

12 years, 8 months

Re: Issue 273 in moose-technology: The Morphic Glamour should update the selectedText in a TextPresentation

by moose-technology＠googlecode.com

Updates: Labels: -Milestone-4.2 Comment #2 on issue 273 by tudor.gi...(a)gmail.com: The Morphic Glamour should update the selectedText in a TextPresentation http://code.google.com/p/moose-technology/issues/detail?id=273 (No comment was entered for this change.)

12 years, 9 months

Issue 492 in moose-technology: Glamour browsers do not release all subscriptions to announcer objects

by moose-technology＠googlecode.com

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-High Component-Glamour Milestone-4.3 New issue 492 by tudor.gi...(a)gmail.com: Glamour browsers do not release all subscriptions to announcer objects http://code.google.com/p/moose-technology/issues/detail?id=492 I noticed that in some complex updating between panels, using an external announcer, some of the update subscriptions were not removed when the browser is closed. I debugged a little and I founded that this implementation: GLMUpdateAction>>unregisterFromAllAnnouncements announcerObjects ifNotNil: [ announcerObjects do: [:each | each unsubscribe: self ] ] is bugged, because if announcerObjects are not previously computed (and in some cases that's what happens), the subscription is not removed. This implementation (just using the accessor instead the direct object), solves the problem (but I don't know is it's a right fix, and it should be a fix in other place) GLMUpdateAction>>unregisterFromAllAnnouncements self announcerObjects ifNotNil: [ :objects | objects do: [:each | each unsubscribe: self ] ] Cheers, Esteban

12 years, 9 months

Moose for SAS

by Ross Boylan

Some people suggested trying moose for analysis of SAS programs, and I'm trying to figure out where to start with the meta-modeling. SAS is not object oriented, though parts of it could be imagined to be. The main SAS code contains blocks of statements that begin with DATA or PROC; each block could probably be thought of as a function--to be precise, the application of a function. If I want to make some new models, where do I start? FM3? FAMIX? elsewhere? The 4.0 release announcement says FM3 and FAMIX3 are both implemented in Fame, so maybe start with Fame? I've read some documentation, but I can't tell. My inspiration for the project is understanding how some SAS datasets were produced. I have a system that creates numerous datasets, which feed into later datasets, etc. This is split at least across a couple of program files and it's really too complicated to keep in the brain. If I get ambitious it would also be useful to trace where particular variables came from, in the sense of both datasets and individual expressions. The only thing resembling a SAS parser I've run into (except for SAS, which is closed source) is a Perl module, and it looked relatively primitive. I've been using PetitParser, and at the point I started thinking about what it would parse results into. Thanks for any pointers. Ross Boylan

12 years, 10 months

Petit SQL Parser

by Fabrizio Perin

Hi all, i did implement an SQL parser using Petit Parser. I toke the grammar specification from SQLite http://www.sqlite.org/lang.html . The grammar implemented is not complete, for now i did implement "just" the create table statement, it means that you should be able to parse at least a script for create the database. The code is in squeaksource http://www.squeaksource.com/@09zbthA-fDDfyUNQ/_OIex3aA . To download it you can evaluate this: Gofer new squeaksource: 'PetitSQLParser'; package: 'ConfigurationOfPetitSQLParser'; load. (Smalltalk at: #ConfigurationOfPetitSQLParser) perform: #loadDefault in the repository there are several packages: the core contains the parser for the grammar. In the package parser there is a parser that instantiate some draft objects representing relational elements. In the next future i will start to implement also other statements. If you start to use it and you have some problem please let me know. Cheers, Fabrizio

12 years, 11 months

Issue 533 in moose-technology: inFusion should export the receiver of invocation

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 533 by tudor.gi...(a)gmail.com: inFusion should export the receiver of invocation http://code.google.com/p/moose-technology/issues/detail?id=533 The receiver should point to a named entity. (FAMIX.Invocation ... (receiver (ref:12)) )

12 years, 11 months

Issue 554 in moose-technology: DSM has flags for refactoring

by moose-technology＠googlecode.com

Status: New Owner: jannik.l...(a)gmail.com Labels: Type-Defect Priority-Medium Milestone-4.4 New issue 554 by jannik.l...(a)gmail.com: DSM has flags for refactoring http://code.google.com/p/moose-technology/issues/detail?id=554 some flags in DSM I should verify for 4.4

12 years, 11 months

Issue 553 in moose-technology: DSM should be split

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: jannik.l...(a)gmail.com Labels: Type-Engineering Priority-Medium Component-DSM Milestone-4.4 New issue 553 by tudor.gi...(a)gmail.com: DSM should be split http://code.google.com/p/moose-technology/issues/detail?id=553 It should be split into generic algorithms (moved to Moose-Algos) and FAMIX specific applications.

12 years, 11 months

← Newer
1
2
3
4
5
6
7
...
12
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev March 2011