Description:
This is a discussion group for Piqi users.
Piqi is a set of languages and tools for working with structured data. Visit http://piqi.org for more information.
|
|
|
piqic-erlang plugin
|
| |
Hi,
I am making a rebar plugin for piqi to reduce number of LOC of Makefiles
in our projects. It works as follows:
{plugins, [piqi_plugin]}.
{piqi_plugin, [
{piqic_erlang, "priv/labels-defs.piqi", ["-I", "priv"]
}
]
...
This works now. However, it fails when we start including headers... more »
|
|
|
How do I create my own types?
|
| |
Say I want to create a custom_type which is the equivalent of pos_integer() How do I go about doing that? As far as I can tell, in the end the type needs to devolve down to one of the pre-defined types (int64, bool, etc.)
|
|
|
How do I get custom_types to dialyze
|
| |
Say I have a type '*foo*', that can only take the values *1..80* I set it up as *.alias [* * .name foo* * .type int64* * .erlang-type "piqirun_custom:foo"* *]* In *piqirun_custom*, I have the following (amongst other stuff) *-type(foo() :: 1..80).* *foo_of_int64(I) when is_integer(I) andalso I >= 1 andalso I =< 80 ->*... more »
|
|
|
piqi RPMs for Fedora in openbuildservice.org
|
| |
Hi all,
I caught up RPM packages with debian ones. The current definitions are
on github[1] and downloads for Fedora are on openbuildservice[2]. It is
mostly `master` branch with patches (1000 and 1001) to make internal
HTML documentation work.
In OBS[3] only Fedora 17 and 18 worked out of the box, others stuck with... more »
|
|
|
Make `tools.md` better suited for `pandoc -t man` (#30)
|
| |
The documentation mangler is done[1], wget --spider does not complain
after these changes, and after some clicking around it seems to look OK.
Now we have these external resources which should stay like that*:
1. /doc/erlang/
2. /doc/piqi-rpc/
And these are now external, but, IMO could be made internal:... more »
|
|
|
bundling manpages and documentation with piqi.rpm
|
| |
Hi Anton,
the initial RPM SPEC for piqi is there[1]. Now it has non-vanilla
/usr/bin/piqi and /usr/bin/piqic 0.6.3. Since package without
documentation is not a package, so I am thinking about adding some man
pages. I have two ideas:
1. Convert doc/*.md to Groff and bundle them as follows:... more »
|
|
|
"default" values in field specifications
|
| |
Hi,
when default value of a field is specified, sometimes leaving no space
between the value "default" is required, and sometimes not. This is
inconvenient, because our piqi definition files are generated (from an
XML) and I have two silly corner cases.
Say we have the following:
.enum [... more »
|
|
|
more protoc troubles with variants and enums
|
| |
Hi Anton, all. I'm trying to convert our piqi files to proto for use with a Python interface and am running into troubles with name collissions. I've narrowed it down to a simple testcase. Is there anything I can do to make this work without rewriting our piqi files, or should I forget about the protobuf... more »
|
|
|
protoc requires globally unique enum values
|
| |
Hi Anton I've run into an issue that I'd like you to comment on. I have one piqi file with two different enums in it, that both have an option 'erlang'. Using piqi to-proto it generates a .proto file without complaints, but when I then run protoc on the file, protoc gives me an error: L087:~/REBAR_DEPS/rmp/src$ protoc --python_out=. types.piqi.proto... more »
|
|
|
