| Age | Commit message (Collapse) | Author | Lines |
|
|
|
|
|
|
|
This would cause pkg-config detection to fail.
I should really write a libpkgconf integration at some point, huh?
|
|
|
|
I didn't catch this in development because macos helpfully zeroes out
all malloc pages on allocation, so my buffers *were* \0-terminated.
Getcbytes is called in a few spots, namely in setopt, and 4 mime
functions.
We only ever call setopt using the partial `pt`, so we can just `comp`
it with `freeze`.
As for mime, we insert a `freeze` in each of the 4 handlers.
Either way, also backport the new getcbytes, which still has the failure
condition, but only under very specific circumstances.
|
|
|
|
I really should do funny jpm alternative things,
there's really no reason for a package manager that strongly depends on
native bindings to not integrate typical tools like pkgconfig.
It's also unfortunate that project.janet cannot have any configure-time
dependencies, meaning that every project needs to duplicate any such
utilities in-line.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TODO: README and other meta-info, this isn't just http anymore
|
|
|
|
|
|
opens the way for static flags once I can test those
|
|
use pkg-config!
the main concern at this point is whether or not adding a "--static" is
safe.
if you don't add "--static", there's no guarantee of static linking.
however, if you do add "--static" but not all of the libraries in
question are available in static form, it will fail to build.
the likely correct way to approach this is to use an env var.
furthermore, I'm not entirely sure as to how/whether the link flags get
passed on to upstream packages.
|
|
new features, yay
|
|
also tests
|
|
|
|
|
|
|
|
|
|
after a short testing period, this'll be released
|
|
to override content-type, simply change the content-type yourself
it's meant to be an "easy to use" API, so defaults etc
|
|
|
|
these are currently to be considered unstable,
fully undocumented.
to be stabilized in an official release later,
assuming they don't need any changes
|
|
|
|
When we initialize an slist but it's meant to be empty,
it might not be zero-allocated and thus recognize it's null.
Therefore, explicitly zero-initialize jurl_cleanup->slist.
|
|
|
|
* adds a getcbytes that accepts any JanetBytes
* use it across the board, except where we can inform curl of the length
|
|
|
|
|
|
|
|
TODO: maybe set up a CHANGELOG?
shotlog is nice and all but you know
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ok not all the tests
just testing the high level api
the other top level things would be:
02-request and 01-native
probably to be done native
mostly useful for regression testing and seeing what went wrong where
for example, if the high level api is what broke, and not request
or if it was the native stuff that broke, and not anything else
etc
|
|
|
|
writing tests reveals issues, as per usual
also rejoice, you have json
I gave up and am depdending on spork/json now
|
|
I really should fix my markdown handling
it should know to use janet formatting inside ```janet
|
|
|
|
|