Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 05 07:34
    Saiv46 commented #86
  • Sep 03 10:34
    rom1504 commented #86
  • Sep 03 10:33
    rom1504 commented #86
  • Sep 03 09:56
    Saiv46 commented #86
  • Sep 02 07:04
    Saiv46 edited #98
  • Sep 02 06:52
    rom1504 commented #98
  • Sep 02 06:49
    Saiv46 commented #98
  • Sep 02 06:48
    Saiv46 commented #98
  • Sep 01 11:18
    rom1504 commented #98
  • Sep 01 11:04
    Saiv46 edited #98
  • Sep 01 11:03
    Saiv46 opened #98
  • Aug 24 16:35
    rom1504 commented #97
  • Aug 24 16:33

    rom1504 on master

    Release 1.6.10 (compare)

  • Aug 24 16:31

    rom1504 on master

    add gitpod and fix gitmodules (compare)

  • Aug 24 16:29
    rom1504 closed #65
  • Aug 24 16:29
    rom1504 commented #65
  • Aug 24 16:28
    rom1504 closed #53
  • Aug 24 16:28
    rom1504 commented #53
  • Aug 24 16:28
    rom1504 closed #52
  • Aug 24 16:28
    rom1504 commented #52
Hans Elias J.
@hansihe
right, yeah
William Gaylord
@wgaylord
And what does prop mean?
Hans Elias J.
@hansihe
that's because I changed the format on the spot, it is not decided yet
Robin Lambertz
@roblabla
I think, it was supposed to be ["virtual", { ref, data, type }]
Right ?
William Gaylord
@wgaylord
if prop means property what does that mean in this case.
Hans Elias J.
@hansihe
prop is a (standardized) way to access a property of another field
Robin Lambertz
@roblabla
prop is the type of reference the virtual is
Hans Elias J.
@hansihe
in this case the "tag" field of the union
so what happens is
Robin Lambertz
@roblabla
(tag, count, ???)
Hans Elias J.
@hansihe
when writing the type out
the virtual field will get it's value from the tag of the union
William Gaylord
@wgaylord
so I will rest my case you your making the Json its own thing that will take a while to learn.
Hans Elias J.
@hansihe
when reading the type, the union will get its value from the virtual field
Robin Lambertz
@roblabla
erm, I meant { ref, prop, type } up there
@chibill we're adding new concepts to protodef. It's obvious that will go in the JSON as well.
William Gaylord
@wgaylord
also you seem to be making the JSON files bigger with out adding anything new to them. Just changing how they work....
Robin Lambertz
@roblabla
The whole idea of the JSON is that it's easier to work with because you don't have to write your own parser and w/e
Hans Elias J.
@hansihe
chibill: what I did was remove hacks that only worked for some special cases and replaced them with more general and expandable mechanisms
case in point, mapper and switch
William Gaylord
@wgaylord
I have no idea why mapper ever existed when you could have just used a switch to do that same job...
Hans Elias J.
@hansihe
both of which were relatively specific, only used in some cases, interacted with each other in a complex way
you can't
that's the point
union is more flexible
it replaces them both
Robin Lambertz
@roblabla
@chibill we needed to put a string in the container to get the name of the packet
We already had switch
The idea was that mapper takes the packet ID and turns it into a packet name
Hans Elias J.
@hansihe
same with the count mechanism in array and buffer
Robin Lambertz
@roblabla
while switch takes the packet ID and figures out what packet type to read from it
Hans Elias J.
@hansihe
that could work in 3 different ways, depending on what arguments you give it
those 3 ways has been replaced with a single way which manages to be generic and not much more verbose
William Gaylord
@wgaylord
switch takes a type and compares it to decide what to do. Mapper takes a type and compares it to decide what to output sounds exactly the same....
waht ever.
Hans Elias J.
@hansihe
yeah. what ever.
it's not though
William Gaylord
@wgaylord
the fact that everything I was working on will be trash pisses me off.
Robin Lambertz
@roblabla
eeh, actually he does have a point. We might've been able to make something better by just creating a "const" type
Hans Elias J.
@hansihe
well, the point of mapper is that it's two way
that's the whole trick of it, if I remember right
William Gaylord
@wgaylord
mapper is one way according to the docs.
Robin Lambertz
@roblabla
@hansihe so for arrays, we could do
def("test") => container(virtual: "true") {
    virtual_field("count", ref: "data", prop: "count") => u64;
    field("data") => array(type: "u8")
}
or something like that ?
Also, what does virtual really do on container ?
William Gaylord
@wgaylord
But I have learned to not trust the docs but this time the Node version agrees.
Hans Elias J.
@hansihe
sorry, I don't quite understand
what do you intend the type: "u8" to do here?
Robin Lambertz
@roblabla
the array's content