With regard to (1), the first place to look is the package homepage on github. You have to scroll down to see the README.md file displayed. searching google with, e.g. for gadfly: "site:github.com Gadfly.jl" (no quotes) gives up these two urls at top.: https://github.com/dcjones/Gadfly.jl dcjones.github.com/Gadfly.jl the https url is package source code home, the person.github.com url is set up docs. All packages have the first, many of the well-tended packages show something useful in that README; fewer have a separate docs portal.
is how I do that. (for gadfly this is https://github.com/dcjones/Gadfly.jl) On Tuesday, July 14, 2015 at 5:47:32 PM UTC-4, Forrest Curo wrote: > > > > On the unpacking issue, rather than put x into a (C type) union, it might > be faster with something like so: > function unpack(x) > x4 = x & 65535 > x3 = ( x >> 16) & 65535 > x2 = (x >> 32) & 65535 > x1 = (x >> 48) & 65535 > return x1, x2, x3, x4 > end > > > but I'd still like simpler explanations of how to write a few lines of C > & render the result callable (maybe without having to make a whole library > of it?). >
