s.gaxie

I am using them as symbols but I need also to get the value of

I am sure there is something to do with regexp but I do not

know how to put away the slash to be able to make the division.

I am working with ratios 
I am using them as symbols but I need also to get the value of
the ratio
I am sure there is something to do with regexp but I do not
know how to put away the slash to be able to make the division.
If someone can help me

syntax-problem

Thanks professor Jourdan !
regexp is realy not fun 
but it works well...
see you

On Jan 19, 2009, at 2:12 PM, s.gaxie wrote:

> I am using them as symbols but I need also to get the value of

> I am sure there is something to do with regexp but I do not

> know how to put away the slash to be able to make the division.

> I am using them as symbols but I need also to get the value of
> the ratio
> I am sure there is something to do with regexp but I do not
> know how to put away the slash to be able to make the division.

Chris Muir
cbm@well.com	
http://www.xfade.com

On 19 janv. 09, at 23:42, Chris Muir wrote:

Hopefully nobody can say it's easier than regexp ;-)

I'm just curious, does anybody know if it's possible to create a 

real-time ac-3 file ( as dolby the protools plugin does) in max to send 

it directly to a dolby receiver/ decoder.

I'm at the beginning of a new project and I want to know it this train 

I'm just curious, does anybody know if it's possible to create a 
real-time ac-3 file ( as dolby the protools plugin does) in max  to send 
it directly to a dolby receiver/ decoder.
I'm at the beginning of a new project and I want to know it this train 
of thought is any good to investigate.

sure regexp is fun but if I have more than one digit 

in my numerator it does not work any more...

sure regexp is fun but if I have more than one digit 
in my numerator it does not work any more...

P.S The "brute force" of Chris does not match also 

ok I get it
regexp becomes realy fun
I had to add this magic symbol : *
thanks Chris and Emmanuel

P.S The "brute force" of Chris does not match also 
with two digits...

This seems to work for dividing two decimals, even with negative numbers although that won't be too important to you in this case I shouldn't think. If you find a problem with it let me know!

On 24 janv. 09, at 01:12, Stefan Tiedje wrote:

> At least its easy to understand, but just by looking at the patch 

> But your regex would also fail with 1.6/4 unless its changed to

> regexp (\d*.*\d)/(\d*.*\d), but that would wrongly accept 1..6/4 

> as well. It seems a perfect solution will always be complicated... ;-)

not really, all that matters is to have enough "expected strings" in 

order to construct the more appropriate regexp. Something like that 

It will also accept toto/titi as a correct result, but on the other 

hand you're never gonna have toto/titi in a umenu made to select ratios.

> At least its easy to understand, but just by looking at the patch  
> I'd say it would fail with 1/16 ...
> But your regex would also fail with 1.6/4 unless its changed to
> regexp (\d*.*\d)/(\d*.*\d), but that would wrongly accept 1..6/4  
> as well. It seems a perfect solution will always be complicated... ;-)

not really, all that matters is to have enough "expected strings" in  
order to construct the more appropriate regexp. Something like that  
will work too:

It will also accept toto/titi as a correct result, but on the other  
hand you're never gonna have toto/titi in a umenu made to select ratios.

syntax problem