| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
| |
* include/yaml.h: fix indentation of comments
* include/yaml.h: fix documentation style comment
* include/yaml.h: fix doc command returns
* include/yaml.h: fix typo
|
| |
|
| |
option can only be ON or OFF. Use set() instead of option() to set default name of target.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In YAML 1.1, the document end marker `...` is optional even if the next document starts with a directive:
https://github.com/yaml/pyyaml/blob/master/tests/data/spec-07-09.canonical
```
%YAML 1.1
---
!!str "foo"
%YAML 1.1
---
!!str "bar"
%YAML 1.1
---
!!str "baz"
```
It is only required if the scalar is "open ended", for example for plain scalars.
In YAML 1.2 the `...` marker is always required before a directive.
My suggestion would be to make the output 1.2 compatible. It will still be 1.1 compatible, so that shouldn't be a problem.
I believe this will also make it easier to fix #123 which was introduced with the last fixes regarding `open_ended`. I think I can make a fix for this soon after this issue is fixed.
Fixing #123 without this would be a bit more complicated.
If we do this, we also need to adjust PyYAML to behave the same.
Related issues/commits:
- https://github.com/yaml/libyaml/issues/60
- https://github.com/yaml/libyaml/pull/122
- 56400d9, 8ee83c0, 56f4b17
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
example-deconstructor-alt.c: In function ‘main’:
example-deconstructor-alt.c:649:51: warning:
comparison between ‘yaml_sequence_style_t {aka enum yaml_sequence_style_e}’
and ‘enum yaml_mapping_style_e’ [-Wenum-compare]
example-deconstructor-alt.c:650:36: warning:
comparison between ‘yaml_sequence_style_t {aka enum yaml_sequence_style_e}’
and ‘enum yaml_mapping_style_e’ [-Wenum-compare]
|
| | |
|
| |
|
|
|
| |
s/intendation/indentation/
Signed-off-by: 林博仁(Buo-ren, Lin) <Buo.Ren.Lin@gmail.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
allow override of Windows static lib name
|
| |/
|
| |
* also changed name back to original default of yaml, as the change in #10 to `yaml_static` broke things that relied on that
|
| |
|
|
| |
Might not be available everywhere
|
| | |
|
| |
|
|
|
|
|
|
| |
I suspect this this was a bit of an oversight when first setting up
appveyor for Windows/msvc, but 'release' does not match any target
cmake knows about; 'Release', however, does.
Signed-off-by: Marty E. Plummer <hanetzer@protonmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
'config.h' is meant to be a convenience header to be #included at build
time, but not installed. Installing it can cause a host of problems for
various other projects (for instance, attempting to build u-boot from
source while another project's 'config.h' exists in the compiler search
path will cause build failures similar to:
https://github.com/pepe2k/u-boot_mod/issues/148
Further, I've changed '#include <config.h>' to '#include "config.h"',
which should constrain the search path to the current build directories,
so if another package with a bugged build has this file installed, it
will not cause yaml to miscompile/fail.
If you have a file `/usr/include/config.h` on your filesystem, query
your package manager to find out what package owns it, and file a bug
report against it with your distro maintainers.
Signed-off-by: Marty E. Plummer <hanetzer@protonmail.com>
|
| |
|
|
| |
Thanks to @tlsa for spotting this
|
| |
|
|
| |
detected by coverity
|
| | |
|
| |
|
|
| |
yaml_emitter_write_indicator const char *indicator
|
| |
|
|
| |
Commit amended by @perlpunk after suggestion from @tlsa
|
| |
|
|
|
| |
we cannot malloc to an anon struct in C++.
typedef yaml_anchors_t
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a followup to #28
See http://yaml.org/spec/1.1/#nb-plain-char(c) and the following
productions.
This commit will allow `[http://example]`, but still fail for:
- `[:foo]`
- `[foo:]`
See https://gist.github.com/perlpunk/de2c631a7b0e9002de351a680eadb573
for all the relevant cases where this change applies.
|
| |
|
|
| |
Remove unneeded context, which is not set in any macro.
|
| | |
|
| |
|
| |
nessesary to necessary
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
if it's on its own line.
```
% cd libyaml
% echo "+STR
+DOC
+SEQ
=VAL '\\\n
-SEQ
-DOC
-STR" | ./tests/run-emitter-test-suite
- '
'
% # fix
% make
...
% echo "+STR
+DOC
+SEQ
=VAL '\\\n
-SEQ
-DOC
-STR" | ./tests/run-emitter-test-suite
- '
'
```
|
| | |
|
| |
|
|
|
|
|
|
| |
(only when explicitly requested)
@jrtc27++ for the patch.
See #60
|
| |
|
|
|
|
|
|
| |
See also issue #60
Revert "This code is not needed and breaks tests"
This reverts commit 56400d976a1999156b1abfd674c3122843980260.
|
| | |
|
| | |
|
| |
|
|
| |
It's just as easy to calculate the maximum value directly.
|
| |
|
|
|
|
|
|
| |
You don't need to specify full paths to files if you do it like this.
Wildcard away most of the stuff you can, and for stuff you can't easily
wildcard, be as generic as you can.
Signed-off-by: Marty E. Plummer <hanetzer@protonmail.com>
|
| |
|
|
|
|
| |
Update the link to point where libyaml is now maintained. Per the old
link, "LibYAML is now maintained at https://github.com/yaml/libyaml.
This page is left for historical purposes."
|
| |
|
|
|
|
|
|
|
|
| |
Currently the cygwin autoconf builds only test builds of cygwin-native
binaries, and not mingw-w64 pure windows binaries. The resultant
cygyaml-0-2.dll has a runtime dep on the cygwin1.dll which is generally
not appropriate for the purpose of distribution. Building with mingw-w64
produces libraries with no dependency on the cygwin runtime.
Signed-off-by: Marty E. Plummer <hanetzer@protonmail.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
repro:
CFLAGS="-Wall -Wextra -Wunused-parameter -Wc++-compat" ./configure && make
which we use for perl, and libyaml is now included in cperl.
Tested with gcc-5 and clang-3.7
There are still a tons of format warnings (%d on 64bit) in
example-deconstructor.c which I skipped.
|
| |
|
|
| |
From https://github.com/ingydotnet/yaml-libyaml-pm/issues/24
|
| |
|
|
|
|
|
|
|
| |
Also reworked all the dockerfiles to be cleaner and consistent:
* Fixed some indentation
* Removed vim dependencies
* Collapsed RUN steps for less build layers
* Renamed dockerfiles/ to shorter and more adaptable docker/
|
| |
|
|
|
|
|
|
| |
Without this change building a dll with the mingw-w64 toolchain is
impossible. All tests from make test-all succeed on native linux
(Gentoo amd64 glibc default/linux/amd64/17.1/desktop gcc-7.2.0)
Signed-off-by: Marty E. Plummer <hanetzer@protonmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the Makefile.am, switched out the fetch (which can have auth problems
in certain envs) with a simple branch per @perlpunk++'s suggestion.
With the new test branches, travis had a problem in that it only clones
one branch and we need the other branch refs to be available. Fixed this
by fetching the other branch refs. I also cleaned up the travis YAML
file.
The Ubuntu 14.04 docker image (used by semaphoreci) had an older git,
without the worktree command, so I made it install the latest git from a
ppa.
Renamed tests/run-tests.sh to tests/run-all-tests.sh for tab completion
conflict reasons.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
with the intent that `make test-suite` will use it as a branch.
This commit makes the libyaml and yaml-test-suite repos completely
independent. The only thing in master is a Makefile rule for
`make run-test-suite`.
The run-test-suite branch takes care of everything else.
This will keep the master branch history clean from any yaml-test-suite
activity, while keeping everything up to date.
Pinning will just work for whatever commit of master you run the tests
from. The pinning work will all be done in the `run-test-suite` branch.
|
| | |
|
