| 2010-06-22 12:02:46 |
Eike |
bug |
|
|
added bug |
| 2010-06-22 12:02:59 |
Eike |
freeode: importance |
Undecided |
Critical |
|
| 2010-06-22 20:18:17 |
Eike |
description |
Interpreter.eval_NodeAttrAccess must be able to look up attributes of unevaluated expressions.
It seems there is a test case missing to test this feature. This is needed for print.
data a:Float variable
print(sqrt(a)) |
Interpreter.eval_NodeAttrAccess must be able to look up attributes of unevaluated expressions.
It seems there is a test case missing to test this feature. This is needed for print.
Expressions that should trigger the bug are:
data a, b: Float variable
print(sqrt(a))
print(a + b)
(a + b).__add__(2)
|
|
| 2010-06-25 20:53:48 |
Eike |
freeode: status |
New |
Confirmed |
|
| 2010-07-10 16:28:28 |
Eike |
tags |
|
interpreter |
|
| 2010-07-11 09:27:12 |
Eike |
freeode: milestone |
|
0.4.1 |
|
| 2010-07-11 09:27:58 |
Eike |
freeode: milestone |
0.4.1 |
0.4.2 |
|
| 2010-11-07 18:34:58 |
Eike |
tags |
interpreter |
expression interpreter |
|
| 2010-11-07 18:39:31 |
Eike |
description |
Interpreter.eval_NodeAttrAccess must be able to look up attributes of unevaluated expressions.
It seems there is a test case missing to test this feature. This is needed for print.
Expressions that should trigger the bug are:
data a, b: Float variable
print(sqrt(a))
print(a + b)
(a + b).__add__(2)
|
Interpreter.eval_NodeAttrAccess must be able to look up attributes of unevaluated expressions.
It seems there is a test case missing to test this feature. This is needed for print.
Expressions that should trigger the bug are:
data a, b: Float variable
print(sqrt(a))
print(a + b)
(a + b).__add__(2)
See: Bug #672227 |
|
| 2010-11-07 18:39:58 |
Eike |
description |
Interpreter.eval_NodeAttrAccess must be able to look up attributes of unevaluated expressions.
It seems there is a test case missing to test this feature. This is needed for print.
Expressions that should trigger the bug are:
data a, b: Float variable
print(sqrt(a))
print(a + b)
(a + b).__add__(2)
See: Bug #672227 |
Interpreter.eval_NodeAttrAccess must be able to look up attributes of unevaluated expressions.
It seems there is a test case missing to test this feature. This is needed for print.
Expressions that should trigger the bug are:
data a, b: Float variable
print(sqrt(a))
print(a + b)
(a + b).__add__(2)
See also:
Bug #672227 |
|
| 2011-06-10 23:19:41 |
Eike |
description |
Interpreter.eval_NodeAttrAccess must be able to look up attributes of unevaluated expressions.
It seems there is a test case missing to test this feature. This is needed for print.
Expressions that should trigger the bug are:
data a, b: Float variable
print(sqrt(a))
print(a + b)
(a + b).__add__(2)
See also:
Bug #672227 |
Interpreter.eval_NodeAttrAccess must be able to look up attributes of unevaluated expressions.
It seems there is a test case missing to test this feature. This is needed for print.
Expressions that should trigger the bug are:
data a, b: Float variable
print(sqrt(a))
print(a + b)
(a + b).__add__(2)
See also:
Bug #672227
http://sourceforge.net/apps/trac/freeode/ticket/7 |
|
| 2012-02-29 20:48:39 |
Eike |
freeode: status |
Confirmed |
In Progress |
|
| 2012-02-29 20:48:39 |
Eike |
freeode: assignee |
|
Eike (eike-welk) |
|
| 2012-02-29 20:48:40 |
Eike |
description |
Interpreter.eval_NodeAttrAccess must be able to look up attributes of unevaluated expressions.
It seems there is a test case missing to test this feature. This is needed for print.
Expressions that should trigger the bug are:
data a, b: Float variable
print(sqrt(a))
print(a + b)
(a + b).__add__(2)
See also:
Bug #672227
http://sourceforge.net/apps/trac/freeode/ticket/7 |
Interpreter.eval_NodeAttrAccess must be able to look up attributes of unevaluated expressions.
It seems there is a test case missing to test this feature. This is needed for print.
Expressions that should trigger the bug are:
data a, b: Float variable
print(sqrt(a))
print(a + b)
(a + b).__add__(2)
data a, b: Float variable
print(sqrt(a))
print(a + b)
(a + b).__add__(2)
An other related issue:
You can look up attributes of the ast.Node itself:
(a + b).function
or
(a + b).loc
This should off course not be possible. Therefore unevaluated expressions need special treatment in Interpreter.eval_NodeAttrAccess(...).
A safe treatment of this situation is:
- Create a variable of the right type and role, and assign the expression to it.
- Do attribute lookups with this variable.
- Optimize the variable away later.
Nearly all lookups are however for methods. They can be processed without constructing an intermediate variable.
See also:
Bug #672227
* Bug #40 - New architecture for code generation in expressions
* NewCodeGenerationArchitecture
http://sourceforge.net/apps/trac/freeode/ticket/7 |
|
| 2012-04-03 08:24:34 |
Eike |
description |
Interpreter.eval_NodeAttrAccess must be able to look up attributes of unevaluated expressions.
It seems there is a test case missing to test this feature. This is needed for print.
Expressions that should trigger the bug are:
data a, b: Float variable
print(sqrt(a))
print(a + b)
(a + b).__add__(2)
data a, b: Float variable
print(sqrt(a))
print(a + b)
(a + b).__add__(2)
An other related issue:
You can look up attributes of the ast.Node itself:
(a + b).function
or
(a + b).loc
This should off course not be possible. Therefore unevaluated expressions need special treatment in Interpreter.eval_NodeAttrAccess(...).
A safe treatment of this situation is:
- Create a variable of the right type and role, and assign the expression to it.
- Do attribute lookups with this variable.
- Optimize the variable away later.
Nearly all lookups are however for methods. They can be processed without constructing an intermediate variable.
See also:
Bug #672227
* Bug #40 - New architecture for code generation in expressions
* NewCodeGenerationArchitecture
http://sourceforge.net/apps/trac/freeode/ticket/7 |
Interpreter.eval_NodeAttrAccess must be able to look up attributes of unevaluated expressions.
It seems there is a test case missing to test this feature. This is needed for print.
Expressions that should trigger the bug are:
data a, b: Float variable
print(sqrt(a))
print(a + b)
(a + b).__add__(2)
data a, b: Float variable
print(sqrt(a))
print(a + b)
(a + b).__add__(2)
An other related issue:
You can look up attributes of the ast.Node itself:
(a + b).function
or
(a + b).loc
This should off course not be possible. Therefore unevaluated expressions need special treatment in Interpreter.eval_NodeAttrAccess(...).
A safe treatment of this situation is:
- Create a variable of the right type and role, and assign the expression to it.
- Do attribute lookups with this variable.
- Optimize the variable away later.
Nearly all lookups are however for methods. They can be processed without constructing an intermediate variable.
See also:
Bug #672227
Bug #672227@trac
* Bug #40@lp - New architecture for code generation in expressions
* Bug #672227 - New architecture for code generation in expressions
* NewCodeGenerationArchitecture
http://sourceforge.net/apps/trac/freeode/ticket/7 |
|
| 2012-04-03 09:01:24 |
Eike |
description |
Interpreter.eval_NodeAttrAccess must be able to look up attributes of unevaluated expressions.
It seems there is a test case missing to test this feature. This is needed for print.
Expressions that should trigger the bug are:
data a, b: Float variable
print(sqrt(a))
print(a + b)
(a + b).__add__(2)
data a, b: Float variable
print(sqrt(a))
print(a + b)
(a + b).__add__(2)
An other related issue:
You can look up attributes of the ast.Node itself:
(a + b).function
or
(a + b).loc
This should off course not be possible. Therefore unevaluated expressions need special treatment in Interpreter.eval_NodeAttrAccess(...).
A safe treatment of this situation is:
- Create a variable of the right type and role, and assign the expression to it.
- Do attribute lookups with this variable.
- Optimize the variable away later.
Nearly all lookups are however for methods. They can be processed without constructing an intermediate variable.
See also:
Bug #672227
Bug #672227@trac
* Bug #40@lp - New architecture for code generation in expressions
* Bug #672227 - New architecture for code generation in expressions
* NewCodeGenerationArchitecture
http://sourceforge.net/apps/trac/freeode/ticket/7 |
Interpreter.eval_NodeAttrAccess must be able to look up attributes of unevaluated expressions.
It seems there is a test case missing to test this feature. This is needed for print.
Expressions that should trigger the bug are:
data a, b: Float variable
print(sqrt(a))
print(a + b)
(a + b).__add__(2)
data a, b: Float variable
print(sqrt(a))
print(a + b)
(a + b).__add__(2)
An other related issue:
You can look up attributes of the ast.Node itself:
(a + b).function
or
(a + b).loc
This should off course not be possible. Therefore unevaluated expressions need special treatment in Interpreter.eval_NodeAttrAccess(...).
A safe treatment of this situation is:
- Create a variable of the right type and role, and assign the expression to it.
- Do attribute lookups with this variable.
- Optimize the variable away later.
Nearly all lookups are however for methods. They can be processed without constructing an intermediate variable.
See also:
* Bug #672227 - New architecture for code generation in expressions
* NewCodeGenerationArchitecture
http://sourceforge.net/apps/trac/freeode/ticket/7 |
|
