Re: [julia-users] Julia implementation

2016-05-25 Thread Scott Jones
>From my own experiences, while I do believe rewriting it in C would make it faster, a much better option would be to adapt JuliaParser.jl. Last year right when I first started with Julia, I thought I'd need to implement most of code that was performance critical (at least for me) in C, and cal

Re: [julia-users] Julia implementation

2016-05-24 Thread Stefan Karpinski
Rewriting the parser in C would (probably) make it faster. So would compiling it using e.g. the recently-open-sourced ChezScheme , which is a less drastic measure. On Tue, May 24, 2016 at 12:47 PM, Ford Ox wrote: > Thank you very much. > > One more question :

Re: [julia-users] Julia implementation

2016-05-24 Thread Ford Ox
Thank you very much. One more question : Is there any speed to gain, when all that stuff would be rewritten in the lowest possible language? (I guess that is assembler or machine code :D)

Re: [julia-users] Julia implementation

2016-05-24 Thread Didier Verna
Stefan Karpinski wrote: > There's something delightful about the fact that in order to change > the syntax of Julia, you must first prove yourself proficient in a > language that actively rejects the very concept of fancy syntax. :-D :-D :-D -- Resistance is futile. You will be jazzimilated.

Re: [julia-users] Julia implementation

2016-05-24 Thread Stefan Karpinski
On Tue, May 24, 2016 at 10:56 AM, Isaiah Norton wrote: > - Scheme: because Julia is a Trojan Horse to finally make the world use > Lisp. because it keeps the pesky peasants out. because it's a great > compiler language and allowed fast implementation and iteration. There is > some interest in mo

[julia-users] Julia implementation

2016-05-24 Thread cormullion
Click on the colored bar on the main page: https://github.com/JuliaLang/julia The current percentage is 66.5% Julia. 2//3... There's some plumbing in C, and the parsing's in Scheme.

Re: [julia-users] Julia implementation

2016-05-24 Thread Isaiah Norton
I would suggest to read src/README.md and the Devdocs ( http://docs.julialang.org/en/latest/devdocs/julia/) for an overview of the organization of the codebase. > What is not implemented in julia? > What language is it implemented in? (I think that arrays come from c, > right?) - frontend (pars

[julia-users] Julia implementation

2016-05-24 Thread Ford Ox
Docs state that most of the julia language is implemented in julia itself. What is not implemented in julia? What language is it implemented in? (I think that arrays come from c, right?) Why is it implemented in that particular language?

Re: [julia-users] Julia implementation of zlib and gzip decompression

2014-01-06 Thread Stefan Karpinski
I kind of figured that, but thought I'd point out its existence anyway. I think it's great to have gzip implemented in pure Julia since there are a lot of cases where all you need is to be able to decompress something and you don't want any dependencies. On Mon, Jan 6, 2014 at 9:15 AM, Gunnar Far

Re: [julia-users] Julia implementation of zlib and gzip decompression

2014-01-06 Thread Gunnar Farnebäck
That's actually also a gzip decompression implementation, so there's a large overlap in that they both implement the inflate algorithm. Otherwise the interfaces are rather different and her implementation includes a visualization branch whereas my implementation is two orders of magnitude faste

Re: [julia-users] Julia implementation of zlib and gzip decompression

2014-01-04 Thread Stefan Karpinski
Possibly relevant is Julia Evan's gzip implementation: http://jvns.ca/blog/2013/10/24/day-16-gzip-plus-poetry-equals-awesome/ On Sat, Jan 4, 2014 at 6:54 AM, Gunnar Farnebäck wrote: > At some point when I had trouble loading zlib I wrote a pure Julia > implementation of zlib and gzip decompress

[julia-users] Julia implementation of zlib and gzip decompression

2014-01-04 Thread Gunnar Farnebäck
At some point when I had trouble loading zlib I wrote a pure Julia implementation of zlib and gzip decompression. Pros: * Written in Julia. * No external dependencies. Cons: * Only supports decompression and only from a buffer (i.e. no streaming). * Substantially slower than zlib (about five tim