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
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@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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev