On 12/10/2010 3:23 AM, Thomas Heller wrote:
I think there is a misunderstanding in how sub-domaining works.
The solution you propose is that a sub domain extends its super domain in
the way that the expressions in the sub domain also become valid in the
super domain. I guess this is the way
Eric Niebler wrote:
On 12/8/2010 5:30 PM, Thomas Heller wrote:
I don't really now how to do it otherwise with the current design.
There is really only this part of the puzzle missing. If it is done, we
have a working and clean Phoenix V3.
For the time being, I can live with the workaround
Eric Niebler wrote:
On 12/10/2010 3:23 AM, Thomas Heller wrote:
snip
However, the solution I am looking for is different.
The sub-domain i tried to define should also extend its super domain, BUT
expressions valid in this sub-domain should not be valid in the super
domain, only in the
On 12/9/2010 10:51 AM, Thomas Heller wrote:
Eric Niebler wrote:
On 12/8/2010 5:30 PM, Thomas Heller wrote:
I don't really now how to do it otherwise with the current design.
There is really only this part of the puzzle missing. If it is done, we
have a working and clean Phoenix V3.
For the
Eric Niebler wrote:
On 12/8/2010 5:30 PM, Thomas Heller wrote:
I don't really now how to do it otherwise with the current design.
There is really only this part of the puzzle missing. If it is done, we
have a working and clean Phoenix V3.
For the time being, I can live with the workaround I
Eric Niebler wrote:
On 12/7/2010 2:37 PM, Thomas Heller wrote:
Hi,
I have been trying to extend a domain by subdomaining it. The sole
purpose of this subdomain was to allow another type of terminal
expression.
Please see the attached code, which is a very simplified version of what
I
On 12/8/2010 5:30 AM, Thomas Heller wrote:
Eric Niebler wrote:
On 12/7/2010 2:37 PM, Thomas Heller wrote:
So, How to handle that correctly?
Yup, that's a problem. I don't have an answer for you at the moment,
sorry.
I think i solved the problem. The testcase for this solution is attached.
Eric Niebler wrote:
On 12/8/2010 5:30 AM, Thomas Heller wrote:
Eric Niebler wrote:
On 12/7/2010 2:37 PM, Thomas Heller wrote:
So, How to handle that correctly?
Yup, that's a problem. I don't have an answer for you at the moment,
sorry.
I think i solved the problem. The testcase for this
Eric Niebler wrote:
On 12/8/2010 4:44 PM, Thomas Heller wrote:
I will try to present a patch. I urgently need this feature to be
become officially supported to use it for phoenix3 (a scope opened by let
or lambda should be it's own sub domains in order to allow local
variables, theses shall
On 12/7/2010 2:37 PM, Thomas Heller wrote:
Hi,
I have been trying to extend a domain by subdomaining it. The sole
purpose of this subdomain was to allow another type of terminal expression.
Please see the attached code, which is a very simplified version of what
I was trying to do.
snip
Eric Niebler wrote:
On 12/7/2010 2:37 PM, Thomas Heller wrote:
Hi,
I have been trying to extend a domain by subdomaining it. The sole
purpose of this subdomain was to allow another type of terminal
expression.
Please see the attached code, which is a very simplified version of what
I
11 matches
Mail list logo
