OK, thanks for the info!
It feels like I am now paying the price for a quick hack that we did a looooong time ago to avoid needing to lookup a type based on incomplete/hard to find information … oh well, I guess this was bound to happen at some time ;-)
On Jun 21, 2013, at 2:54 PM, Tudor Girba tudor@tudorgirba.com wrote:
Hi,
4.3 is rather long time ago, and it is likely that indeed the opposite relation was added afterwards. However, declaredType: should have always receive a type, not a string. So, the error comes from the place in your code in which you are storing a string in declaredType.
Cheers, Doru
On Fri, Jun 21, 2013 at 7:55 PM, Johan Fabry jfabry@dcc.uchile.cl wrote:
The not very helpful reply is "because all the code worked in 4.3". what I need to figure out is whether this bug I have now is caused here or if there is something going wrong upstream. From your reply I guess this is the latter. So I need to know (ideally) what changes to FAMIX between 4.3 and 4.8 could have caused this to happen.
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile