Flee Work Item Rss Feed

Commented Issue: Silverlight compatibility [8121]

doozel — Fri, 02 Oct 2009 03:38:15 GMT

Is it possible?
Comments: ** Comment from web user: doozel **

I converted a previous version of Flee to Silverlight, works nicely. Emit does work but you can't specify your expression owner, it is marked as internal in Silverlight.

Commented Issue: Silverlight compatibility

Pelmen64 — Sat, 25 Jul 2009 17:06:00 GMT

Is it possible?
Comments: ** Comment from web user: Pelmen64 **

Silverlight doesn't allow you to use Reflection.Emit, so it's not possible to use code generation (that FLEE does).

Commented Feature: Implicit multiplication

denism7 — Thu, 23 Jul 2009 10:16:49 GMT

I have suggestion for expression parser. It would be useful to recognize variable or function with multiplier (without multiplication sign) and convert it to appropriate IL-instruction.

I think, it makes expression like "2pi + 3 sin(x^2)" more lightweight.
Comments: ** Comment from web user: denism7 **

It's not necessary to handle post-bracket implicit multiplication. The central idea is making some operations with custom types more flexible and transparent. For example, '2 months + 3 years' looks much better than '2 * months + 3 * years'.

Commented Feature: Implicit multiplication

denism7 — Thu, 23 Jul 2009 10:01:11 GMT

There is no ambiguity because it works only for numbers before variable, constant or function and optionally before and after brackets like 2(3+1) or (2+3)x. Only side effect is possible when using exponential form numbers like 2e-1. It's also perfect way to support complex numbers. You just need define constant i = Complex(0, 1) and override some arithmetic operators.

Created Issue: Silverlight compatibility

denism7 — Wed, 22 Jul 2009 14:49:06 GMT

Is it possible?

Closed Issue: Allow to supply an IFormatProvider when compiling an expression

ECiloci — Thu, 16 Jul 2009 13:34:34 GMT

Thank you for this great project! I came across the following issue:

Depending on the configured culture, different decimal separators are used. Independent of the configured culture, I would always like to use a decimal point as the separator. Therefore I suggest to add an overload for ExpressionContext.CompileDynamic and ExpressionContext.CompileGeneric which takes an IFormatProvider as an argument.
Comments:

Commented Issue: Allow to supply an IFormatProvider when compiling an expression

Schlotter — Wed, 15 Jul 2009 08:43:16 GMT

Thank you! Works for me...

Commented Issue: Allow to supply an IFormatProvider when compiling an expression

ECiloci — Wed, 15 Jul 2009 02:42:13 GMT

The decimal point takes its default value from the current culture but it can be overridden using the ParserOptions.

See here:
http://flee.codeplex.com/Wiki/View.aspx?title=CustomizingParser

Created Issue: Allow to supply an IFormatProvider when compiling an expression

Schlotter — Thu, 09 Jul 2009 09:16:27 GMT

Commented Feature: Implicit multiplication

ECiloci — Fri, 03 Jul 2009 02:18:14 GMT

Sorry for being so late on this.

With this approach, there is an ambiguity for expressions with subtraction:
(2+3) - 2
Is treated as (2 + 3) * -2
How do you think this should be handled?

Commented Feature: Configurable string separator

ECiloci — Wed, 24 Jun 2009 00:33:30 GMT

Hi,

I want to use your parser together with XAML, by implementing a markup extension which would execute Flee expressions. The expressions are going to be specified in XAML, inside of markup extension like this:
Value="{Expression '123+456'}"
Because the markup expression is already enclosed in double-quotes, and single quotes are used for surrounding Flee expression, I need another character to be used as the string separator. Escaping every character doesn't seem nice in this case.
I quickly modified the source and it seems to work if I change double-quotes to tilde ` character.
So XAML looks like this now:
<TextBlock Text="{ex:Expression '`123` + 456'}"/>
It would be nice if there was simply an option in ParserOptions that would allow to change that on-the-fly, instead of recompiling the source.

Thanks.

Denis
Comments: ** Comment from web user: ECiloci **

Looks like a straightforward parser option. I'll try to have it in the next release (couple of weeks to a month)

Created Issue: Configurable string separator

denismo — Sun, 21 Jun 2009 12:23:22 GMT

Closed Issue: DateTime evaluation fails

ECiloci — Sun, 26 Apr 2009 01:50:02 GMT

This is a great library, but I ran into an issue where greater than, less than fail for DateTime values.

ExpressionContext ec = new ExpressionContext();
ec.Variables.Add("o", new DateTime(2009, 4, 10) );
IGenericExpression<bool> e = ec.CompileGeneric<bool>("o >= #04/08/2009#");
Assert.IsTrue(e.Evaluate());

I had to get it working by using this syntax

ExpressionContext ec = new ExpressionContext();
ec.Variables.Add("o", new DateTime(2009, 4, 10));
IGenericExpression<bool> e = ec.CompileGeneric<bool>("o.Year = 2009 And o.Month >= 4 And o.Day >= 8");
Assert.IsTrue(e.Evaluate());
Comments: Not a bug

Commented Issue: DateTime evaluation fails

ECiloci — Sun, 26 Apr 2009 01:49:16 GMT

Nevermind. Due to some other bug fixes, I've made the default format for date literals be the short date format of the current culture. The change is in v0.9.25.0.

Commented Issue: Implicit multiplication

ECiloci — Wed, 22 Apr 2009 03:03:27 GMT

I'll see what I can do.

Commented Issue: DateTime evaluation fails

ECiloci — Wed, 08 Apr 2009 02:25:06 GMT

>Would it be difficult to change the default format to the System.Globalization.CultureInfo.CurrentCulture.DateTimeFormat.ShortDateFormat ?
I've made the other syntax customization properties have to be explicitly set, so making the format implicit to the current culture would make things inconsistent.

Created Issue: Implicit multiplication

denism7 — Mon, 06 Apr 2009 12:07:05 GMT

Commented Issue: DateTime evaluation fails

TerryDenham — Sat, 04 Apr 2009 16:24:03 GMT

Would it be difficult to change the default format to the System.Globalization.CultureInfo.CurrentCulture.DateTimeFormat.ShortDateFormat ?

Either way, I'll fix my code. Thanks for replying and thanks for a great library.

Closed Issue: Illegal one-byte branch error in version 0.9.23.0

ECiloci — Sat, 04 Apr 2009 02:07:13 GMT

I have the following expression that give me the:

System.NotSupportedException: Illegal one-byte branch at position: 118. Requested branch was: 143.
at System.Reflection.Emit.ILGenerator.BakeByteArray()
at System.Reflection.Emit.DynamicResolver..ctor(DynamicILGenerator ilGenerator)
at System.Reflection.Emit.DynamicILGenerator.GetCallableMethod(Void* module)
at System.Reflection.Emit.DynamicMethod.GetMethodDescriptor()
at System.Reflection.Emit.DynamicMethod.CreateDelegate(Type delegateType)
at Ciloci.Flee.Expression`1.Compile(String expression, Object owner, ExpressionOptions options)
at Ciloci.Flee.Expression`1..ctor(String expression, ExpressionContext context)
at Ciloci.Flee.ExpressionFactory.CreateGeneric[T](String expression, ExpressionContext context)
at ExpressionEval.CreateGenericExpression[T](String expression, ExpressionContext context)
at ExpressionEval.Evaluate(String expression)
at StrategyHelper.DoExpression(Guid modelEntityId, ClaimMaster claim)

(((((402 >= 360 AND 402 <= 361))) OR (((402 >= 369 AND 402 <= 369))) OR (((402 >= 490 AND 402 <= 490))) OR (((402 >= 499 AND 402 <= 499)))) AND (((("76856" = "47562" OR "76830" = "47562") OR ("76856" = "47563" OR "76830" = "47563") OR ("76856" = "47564" OR "76830" = "47564"))))) OR (((402 >= 360 AND 402 <= 361) OR (402 >= 369 AND 402 <= 369) OR (402 >= 490 AND 402 <= 490) OR (402 >= 499 AND 402 <= 499)) AND (("76856" = "47562" OR "76830" = "47562") OR ("76856" = "47563" OR "76830" = "47563") OR ("76856" = "47564" OR "76830" = "47564")))

If I break the expression up like so and run each separately they work, but error out when run together:

(((((402>=360 AND 402<=361))) OR (((402>=369 AND 402<=369))) OR (((402>=490 AND 402<=490))) OR (((402>=499 AND 402<=499)))) AND (((("76856"="47562" OR "76830"="47562") OR ("76856"="47563" OR "76830"="47563") OR ("76856"="47564" OR "76830"="47564")))))

OR

(((((402>=360 AND 402<=361))) OR (((402>=369 AND 402<=369))) OR (((402>=490 AND 402<=490))) OR (((402>=499 AND 402<=499)))) AND (((("76856"="47562" OR "76830"="47562") OR ("76856"="47563" OR "76830"="47563") OR ("76856"="47564" OR "76830"="47564"))))

I have the latest code, version 0.9.23.0
Comments: Fixed in 0.9.24.0

Closed Issue: Illegal one-byte branch error

ECiloci — Sat, 04 Apr 2009 02:06:11 GMT

The following expression:

(((((402 >= 360 AND 402 <= 361))) OR (((402 >= 369 AND 402 <= 369))) OR (((402 >= 490 AND 402 <= 490))) OR (((402 >= 499 AND 402 <= 499)))) AND (((("76856" = "47562" OR "76830" = "47562") OR ("76856" = "47563" OR "76830" = "47563") OR ("76856" = "47564" OR "76830" = "47564"))))) OR (((402 >= 360 AND 402 <= 361) OR (402 >= 369 AND 402 <= 369) OR (402 >= 490 AND 402 <= 490) OR (402 >= 499 AND 402 <= 499)) AND (("76856" = "47562" OR "76830" = "47562") OR ("76856" = "47563" OR "76830" = "47563") OR ("76856" = "47564" OR "76830" = "47564")))

produces the following exception when compiled:
System.NotSupportedException: Illegal one-byte branch at position: 118. Requested branch was: 143.

The issue was reported in thread #51304
Comments: duplicate of #7418