Closed aktau closed 6 years ago
Yes I am aware of that. Documentation and examples are all still stuck in 1.x land :smile:
There's not a whole lot of (user-facing) things that are done yet. In general I've tried to be more compatible with DTrace's syntax wherever possible. http://dtrace.org/guide is my bible. Simple aggregations should work, but have a slightly different syntax vs. 1.x:
ply 'k:SyS_read { @[comm] = quantize(arg2); }'
I imagine three layers of testing. The first is obviously unittesting. The second is the method you're describing, the ply part of this is already there (run ply with -e
, also add -S
to see a dump of the compiled program). The third involves creating a set of small executables with known calling patterns, and then tracing these with ply as they are executed, verifying the ply output against expected values. Almost none of this is in place today, but it is in The Plan :wink:
Thank you for those kind words.
Fixed in 811a515f229fbc9490ea1f610621462e22adb3b3
You're probably aware of this, I just wanted to try it out. Do you have some updated scripts which work? I assume you try running it after making a change :D.
It might be nice to have a "compile-but-don't-execute" mode so that you can run some CI (travis) on every commit.
Thanks for ply(1), it's the neatest little bytecode compiler I know.