skaller wrote:
> BTW: I just posted some mail to my dummy group.
>
> Neither of the registered 'me' actually got it (so far)
>
> I know it turned up, it is visible from the web.
>
> The second me made this post, avoiding the posting
> error from the first one (posting from different
> email address
Every time I run my parser, it always has at least one unreachable
nonterminal. Looking at the grammar that felix generates, it's easy to
see the problem:
nonterm(_poly_3928t_6311*) elk_1 {
-> t:TOK_TEXT
{
_poly_3928t_6311 *_x = new
_poly_3928t_6311(_nt_1007_1009(FLX_FPAR_PASS ptrc
Playing around with the parser for the first time, and I got some
comments. First, I parse should return an opt instead of an anonymous
union. See here, on line 52:
http://felix.sourceforge.net/doc/tutorial/introduction/en_flx_tutorial_0070.html
51: match z with
52: | case 0 => { pr
On Sat, 2007-03-24 at 16:54 -0700, Erick Tryzelaar wrote:
> Currently if you have a formatting string f"%s", it expects a charp
> instead of a string. To get the string, you need f"%S". Since I'd expect
> that felix strings will be used much more often than charps, mind if I
> swap the two meani
On Sat, 2007-03-24 at 16:11 -0700, Erick Tryzelaar wrote:
> I found an interesting case using Array::find. find has two function
> signatures:
>
> fun find[T, N] (eq:T->bool) (x:array[T, N]): opt[T]
> fun find[T, N] (eq:T*T->bool) (x:array[T, N]) (e:T): opt[T]
>
> This is all fine, except when
On Sat, 2007-03-24 at 16:52 -0400, Chris King wrote:
> On 3/24/07, Erick Tryzelaar <[EMAIL PROTECTED]> wrote:
> > How
> > difficult would it be to support something like this?
> >
> > regmatch "host:/foo/bar/baz" with
> > | ((alphanumeric+ as ?host) ":" (_* as ?path)) as ?arg => Some (arg,
> > host
On Sat, 2007-03-24 at 13:29 -0700, Erick Tryzelaar wrote:
> Python, as you probably know, has the feature for matching
> subexpressions in a regular expression, like this:
> I don't see an easy way on how to do this.
Tre can do it using Posix standard syntax.
> reglex seems like it could work
Currently if you have a formatting string f"%s", it expects a charp
instead of a string. To get the string, you need f"%S". Since I'd expect
that felix strings will be used much more often than charps, mind if I
swap the two meanings?
Also, once we roll out the show typeclass, we probably shoul
I found an interesting case using Array::find. find has two function
signatures:
fun find[T, N] (eq:T->bool) (x:array[T, N]): opt[T]
fun find[T, N] (eq:T*T->bool) (x:array[T, N]) (e:T): opt[T]
This is all fine, except when the array you're working with is an array
of tuples, like this:
val a
Chris King wrote:
> I'm a bit confused by the subject of your e-mail... I meant "classes"
> in the context of "school", not "objects" :) In which case the answer
> is I plan to extend Felix's current implementation with the data
> structures necessary to support Laurikari's NFA extensions. Or did
On 3/24/07, Erick Tryzelaar <[EMAIL PROTECTED]> wrote:
> > I volunteered to take a stab at implementing it after classes
> > get out, as my first foray into Felix's source code (presuming someone
> > else doesn't beat me to it).
>
> What are you planning to do?
I'm a bit confused by the subject of
> I volunteered to take a stab at implementing it after classes
> get out, as my first foray into Felix's source code (presuming someone
> else doesn't beat me to it).
>
> - Chris
What are you planning to do?
-e
-
Take Surv
On 3/24/07, Erick Tryzelaar <[EMAIL PROTECTED]> wrote:
> How
> difficult would it be to support something like this?
>
> regmatch "host:/foo/bar/baz" with
> | ((alphanumeric+ as ?host) ":" (_* as ?path)) as ?arg => Some (arg,
> host, port)
> | _ => None
> endregmatch;
I thought Felix did this alre
Python, as you probably know, has the feature for matching
subexpressions in a regular expression, like this:
>>> m = re.search(r'((\w+):(.*))', 'host:/foo/bar/baz')
>>> m.groups()
('host:/foo/bar/baz', 'host', '/foo/bar/baz')
or:
>>> m = re.search(r'(?P(?P\w+):(?P.*))',
'host:/foo/bar/baz'
14 matches
Mail list logo
