Looks like a really helpful report – thanks!

On 3 April 2015 at 16:38, Siyi Deng <[email protected]> wrote:

> Hi, following your suggestion, I opened a new issue on Julia repo:
> https://github.com/JuliaLang/julia/issues/10734
>
>
> On Friday, April 3, 2015 at 7:15:19 AM UTC-7, Mike Innes wrote:
>>
>> Would you be able to produce a minimal test case that works in the 0.3.4
>> REPL but not in 0.3.7, then file that as an issue on the Julia repo?
>>
>> On 3 April 2015 at 15:09, Siyi Deng <[email protected]> wrote:
>>
>>> Hi Mike:
>>> I followed your suggestion , the Julia version used by Juno was 0.3.4
>>> and the standalone REPL was 0.3.7 (all x86_64-w64-mingw32), so indeed it
>>> seems that new version introduced a bug of some kind.
>>>
>>>
>>>
>>>
>>>
>>> On Friday, April 3, 2015 at 3:12:47 AM UTC-7, Mike Innes wrote:
>>>>
>>>> Well, this is the first time it's happened this way around :)
>>>>
>>>> The first thing I would do is open the copy of Julia that Juno is
>>>> running using the "open a terminal" command, and see whether that gives the
>>>> right results. If the version is different, a bug may have been introduced
>>>> by a backport or something similar.
>>>>
>>>> On 3 April 2015 at 05:50, Kevin Squire <[email protected]> wrote:
>>>>
>>>>> Hi Siyi,
>>>>>
>>>>> Can you give a short example of your code?  It's generally pretty hard
>>>>> to debug these things without that.
>>>>>
>>>>> Cheers!
>>>>>    Kevin
>>>>>
>>>>> On Thursday, April 2, 2015, Siyi Deng <[email protected]> wrote:
>>>>>
>>>>>> Hi,
>>>>>> I have created a c shared library using visual-studio; then I called
>>>>>> the c functions in Juno IDE, everything worked as expected.
>>>>>>
>>>>>> Then I installed the julia command line version, and ran the same
>>>>>> script again, and this time it seems that the c functions has not been
>>>>>> called properly, no exception was thrown, but the functions never return
>>>>>> meaningful values.
>>>>>>
>>>>>> I was using the 64bit stable release in both cases.
>>>>>>
>>>>>> Any insight? Thanks!
>>>>>>
>>>>>
>>>>
>>

Reply via email to