I bet it's the same problem as this:
https://www.mail-archive.com/picolisp@software-lab.de/msg04411.html

emscripten uses clang, right?


On Fri, May 9, 2014 at 1:59 PM, Rick Lyman <lyman.r...@gmail.com> wrote:

> just a note:
>
> Downloaded miniPicoLisp.
> Building under Linux/gcc ok
>
> Downloaded Emscripten (for Windows)
> Using c files (from Linux re: above) I tried: "emcc -O2 flow.c -o flow.bc"
>
> below are a few of the errors generated:
>
> flow.c:41:62: warning: '&&' within '||' [-Wlogical-op-parentheses]
>    if (isNum(x = EVAL(x)) || isNil(x) || x == T || isCell(x) &&
> isNum(car(x)))
>                                                 ~~
> ~~~~~~~~~~^~~~~~~~~~~~~~~~
> flow.c:41:62: note: place parentheses around the '&&' expression to
> silence this
>
>       warning
>    if (isNum(x = EVAL(x)) || isNil(x) || x == T || isCell(x) &&
> isNum(car(x)))
>
>  ~~~~~~~~~~^~~~~~~~~~~~~~~~
> flow.c:60:37: error: fields must have a constant size: 'variable length
> array in
>
>       structure' extension will never be supported
>          struct {any sym; any val;} bnd[length(x)];
>                                     ^
> flow.c:77:18: warning: using the result of an assignment as a condition
> without
>       parentheses [-Wparentheses]
>       } while (p = p->link);
>                ~~^~~~~~~~~
>
> ...
>
>
>
>
> On Fri, May 9, 2014 at 11:20 AM, Rick Lyman <lyman.r...@gmail.com> wrote:
>
>> re: http://pypyjs.org/demo/
>>
>> Success:
>> Chrome: 34
>> Internet Explorer: 11
>>
>> Failure:
>> Safari: 5
>>
>>
>> On Fri, May 9, 2014 at 10:50 AM, Joe Bogner <joebog...@gmail.com> wrote:
>>
>>> It works in chrome too and IE10 too
>>>
>>> Check out: http://pypyjs.org/demo/
>>>
>>>
>>>
>>>
>>> On Fri, May 9, 2014 at 10:21 AM, Rick Lyman <lyman.r...@gmail.com>wrote:
>>>
>>>> Joe, Christophe,
>>>>
>>>> A downside to asm.js is that it is Firefox only...
>>>>
>>>>
>>>> http://www.infoworld.com/t/javascript/apple-has-its-own-javascript-accelerator-in-the-works-242042
>>>>
>>>> -rl
>>>>
>>>> p.s.: anyone considering c directly via Chrome/NaCL?
>>>>
>>>>
>>>> On Fri, May 9, 2014 at 8:19 AM, Joe Bogner <joebog...@gmail.com> wrote:
>>>>
>>>>> Hi Rick, Christophe,
>>>>>
>>>>> I was thinking the same thing. miniPicolisp might be a simpler first
>>>>> step to port
>>>>>
>>>>>
>>>>> On Fri, May 9, 2014 at 7:51 AM, Rick Lyman 
>>>>> <lyman.r...@gmail.com<lymanr...@gmail.com>
>>>>> > wrote:
>>>>>
>>>>>> Christophe,
>>>>>>
>>>>>> How about porting the c version using:
>>>>>> https://github.com/kripken/emscripten?
>>>>>>
>>>>>> -rl
>>>>>>
>>>>>>
>>>>>> On Thu, May 8, 2014 at 5:08 PM, Christophe Gragnic <
>>>>>> christophegrag...@gmail.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I'm currently embedding a «pedagogical pseudo-code like language» in
>>>>>>> PicoLisp.
>>>>>>> As using plain browsers is a nice thing to have in front of students,
>>>>>>> I tried with
>>>>>>> EmuLisp (PicoLisp in JS, by Jon Kleiser, that I won't thank enough,
>>>>>>> with Alex),
>>>>>>> which proved to be a good solution for me.
>>>>>>>
>>>>>>> So I had some thoughts, ideas and questions.
>>>>>>>
>>>>>>> 1) EmuLisp lacks some functions. The first idea I had was to write
>>>>>>> them in the
>>>>>>> available functions (like 'glue' with 'pack'). It worked for some,
>>>>>>> but
>>>>>>> some others
>>>>>>> needed to be implemented in JS. Now my question: how far could be
>>>>>>> pushed the
>>>>>>> idea to write a maximal subset of Picolisp in a minimal subset of
>>>>>>> Picolisp? Like in
>>>>>>> the original paper of McCarthy or «the Jewel» in SICP? I'm not
>>>>>>> talking about
>>>>>>> performance here, just functions availability.
>>>>>>>
>>>>>>> 2) Since PicoLisp64 is written in a «generic assembly» embedded in
>>>>>>> PicoLisp,
>>>>>>> I was wondering (only wondering, since the concepts are a bit vague
>>>>>>> for me) if
>>>>>>> instead of building the .s files we could build some
>>>>>>> http://asmjs.org/ file(s).
>>>>>>>
>>>>>>> 3) Regarding EmuLisp again, and for your information, I've created
>>>>>>> (and am using seriously!) a JS pil, that I named `piljs` which runs
>>>>>>> on node
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

Reply via email to