Is Coral using the Opal compiler for its syntax extensions?
it extends petitParser.
Now the challenges of Coral are not in the syntax. But
How can we call system call, how can we manipule OS variable.
How can we edit a "script" and debug it inside the image and publish it
as a dead file.
Remember Coral is not about forcing us to edit in vim, but to have a
living scripts that
we be debugged and published as dead files or zombified on demand.
Stef
- Francisco
On 3 Jun 2015, at 16:21, Marcus Denker <[email protected]> wrote:
On 03 Jun 2015, at 17:12, Ben Coman <[email protected]> wrote:
On Wed, Jun 3, 2015 at 4:14 PM, Francisco Garau
<[email protected]> wrote:
On 3 June 2015 at 05:56, Ben Coman <[email protected]> wrote:
I think that would confuse me, and maybe break syntax highlighting.
It *looks* like a message send to nothing.
That might be a good thing as there is no object needed to resolve the
method lookup. You already have the "method" to evaluate, which is obviously
the block.
It's a bit heretic, but the more I think, the more I like it.
Well, if its an itch you need to scratch, go ahead :)
But it might be a struggle to get the community to accept it into
Pharo, and hence possibly a maintenance burden for you each Pharo
release.
It would make a nice tutorial how to hack the compiler for experiments…
Marcus
