0005035: expr.{expr} form not documented

(0005955)
doligez (manager)
2011-06-01 22:49

Should this be documented in chapter 7?

(0005986)
lavi (reporter)
2011-06-07 11:08

Another sligthly related wish: It would be nice if documentation clearly specify which function is called for which construction (this is the same with expression expr.(expr) and expr.[expr]). So that reuse of those syntax would not be left unspecified.

(0008868)
doligez (manager)
2013-02-19 11:46

Original PR: fixed (commit 13301), including documentation of the functions called for expr.{expr} and expr.{expr}<-expr.

I don't think we want to document the functions called for expr.(expr) and expr.[expr] because:
1. we don't want to encourage people to redefine them
2. we want to be able to change them in the future (for example when we implement namespaces)

Issue History
Date Modified	Username	Field	Change
2010-04-24 05:48	kaustuv	New Issue
2011-06-01 22:49	doligez	Note Added: 0005955
2011-06-01 22:49	doligez	Status	new => acknowledged
2011-06-07 11:08	lavi	Note Added: 0005986
2012-09-06 16:44	doligez	Target Version	=> 4.00.1+dev
2012-09-17 17:57	doligez	Relationship added	duplicate of 0003688
2012-09-17 17:58	doligez	Target Version	4.00.1+dev => 4.00.2+dev
2013-02-19 11:46	doligez	Note Added: 0008868
2013-02-19 11:46	doligez	Status	acknowledged => resolved
2013-02-19 12:55	doligez	Resolution	open => fixed

Notes
(0005955) doligez (manager) 2011-06-01 22:49	Should this be documented in chapter 7?

(0005986) lavi (reporter) 2011-06-07 11:08	Another sligthly related wish: It would be nice if documentation clearly specify which function is called for which construction (this is the same with expression expr.(expr) and expr.[expr]). So that reuse of those syntax would not be left unspecified.

(0008868) doligez (manager) 2013-02-19 11:46	Original PR: fixed (commit 13301), including documentation of the functions called for expr.{expr} and expr.{expr}<-expr. I don't think we want to document the functions called for expr.(expr) and expr.[expr] because: 1. we don't want to encourage people to redefine them 2. we want to be able to change them in the future (for example when we implement namespaces)