8 Sep
2014
8 Sep
'14
4:23 p.m.
Hi, when trying out the new pillar inspector (Great!)
I noticed some issues with PetitTest and PetitAnalyzer.
Their packages are dirty after
#ConfigurationOfPetitParserIslands asClass loadDevelopment.
I've tried it on Pharo For The Enterprise
Much easier to use than a plain text viewer.
Here are some more common constructs to handle:
- ending a code block with]]] at the end of line
- ClassName>>methodName
- ClassName class>>methodName
Stephan
8 Sep
8 Sep
4:27 p.m.
Hi,
Indeed, I know about the dirty packages. They will be gone once island
parsing will be integrated into PetitParser. It's my way of incentivising
Jan :)
Doru
On Mon, Sep 8, 2014 at 4:23 PM, Stephan Eggermont <stephan(a)stack.nl> wrote:
Hi, when trying out the new pillar inspector (Great!)
I noticed some issues with PetitTest and PetitAnalyzer.
Their packages are dirty after
#ConfigurationOfPetitParserIslands asClass loadDevelopment.
I've tried it on Pharo For The Enterprise
Much easier to use than a plain text viewer.
Here are some more common constructs to handle:
- ending a code block with]]] at the end of line
- ClassName>>methodName
- ClassName class>>methodName
Stephan
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every thing has its own flow"
3521
days inactive
3521
days old
1 comments
2 participants
participants (2)
-
Stephan Eggermont -
Tudor Girba