Re: [DISCUSS] wrong conversion typisation in SCD source

2017-07-11 Thread Timothee Maret
Thanks Simo! Cheers, Tim 2017-07-11 13:57 GMT+02:00 Simone Tripodi : > Verified in r1801580[0] > best, > -Simo > > [0] https://svn.apache.org/viewvc?view=revision=1801580 > > http://people.apache.org/~simonetripodi/ > http://twitter.com/simonetripodi > > On Tue, Jul

Re: [DISCUSS] wrong conversion typisation in SCD source

2017-07-11 Thread Simone Tripodi
Verified in r1801580[0] best, -Simo [0] https://svn.apache.org/viewvc?view=revision=1801580 http://people.apache.org/~simonetripodi/ http://twitter.com/simonetripodi On Tue, Jul 11, 2017 at 11:22 AM, Simone Tripodi wrote: > Hi mates, > I verified with a test case &

Re: [DISCUSS] wrong conversion typisation in SCD source

2017-07-11 Thread Simone Tripodi
Hi mates, I verified with a test case & the debugger that the warning is not harmful and that can be suppressed, the only issue is at compile time but at runtime typisation is correct. Sorry for the noise! -Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Jul 11,

Re: [DISCUSS] wrong conversion typisation in SCD source

2017-07-10 Thread Tommaso Teofili
+1 thanks Simo Il giorno lun 10 lug 2017 alle 16:30 Timothee Maret ha scritto: > Hi Simo! > > I guess the best is to JIRA with a failing test :-) > I don't think this is tracked anywhere. > > Cheers, > > Timothee > > 2017-07-10 15:05 GMT+02:00 Simone Tripodi

Re: [DISCUSS] wrong conversion typisation in SCD source

2017-07-10 Thread Timothee Maret
Hi Simo! I guess the best is to JIRA with a failing test :-) I don't think this is tracked anywhere. Cheers, Timothee 2017-07-10 15:05 GMT+02:00 Simone Tripodi : > Hi mates, > there still is a completely wrong type conversion in the source code which > can

[DISCUSS] wrong conversion typisation in SCD source

2017-07-10 Thread Simone Tripodi
Hi mates, there still is a completely wrong type conversion in the source code which can potentially throw unexpected troubles... Did you have a chance already to have a look at it? Would it be ok filling an issue to track it and avoid to release such error in the next release? TIA! -Simo [1]