Viewing profile — lhoursquentin
lhoursquentin
HN member- Joined
- Tue, Feb 11, 2020, 6:36 AM UTC
- HN karma
- 102
- Public activity
- 23 items
- HN profile
- View on Hacker News ↗
About lhoursquentin
No profile information was provided.
Recent public activity
- comment
-
comment
Comment #33355543
The lack of arrays, dicts and local variables when trying to be POSIX compliant becomes quickly annoying when writing big programs though. There are of course workarounds to deal w…
-
comment
Comment #33355315
What's interesting with this example of command1 | command2 is that some shells such as zsh will optimize the last member of the pipeline to be executed in the current process (not…
-
comment
Comment #33354759
> [[ ]] is a bash builtin, and is more powerful than [ ] or test. Agreed on the powerful bit, however [[ ]] is not a "builtin" (whereas [ and test are builtins in bash), it's a res…
- story
-
comment
Comment #31597703
> Yeah, I know there's D3.js but that involved way more knowledge and learning than I was interested in. Same, d3 looked very powerful but had a steep learning curve. I was looking…
- story
-
comment
Comment #29885180
https://www.grymoire.com/Unix/Sed.html is a good resource to get started, though it's definitely something you should not just read due to the fact that sed code is pretty hard to …
-
comment
Comment #29052342
> I would be curious if mksh is also faster. ksh93 also claims great performance increases, but it is no longer (well) maintained. mksh `printf` is not builtin, so if the script ma…
-
comment
Comment #25155744
Cool I'll definitely try to set it up in the coming days! Here's my humble strace visualizer: https://lhoursquentin.github.io/visual-strace/
-
comment
Comment #25154522
Great post, also love what you are trying to do with C playground, this is awesome! I've recently been trying to build something similar, visualizing forks/exeve/read/write, but us…
-
comment
Comment #24541641
You should probably note that this hack spawns an additional shell process per comment :)
-
comment
Comment #24519623
Yes most of the time the respecting POSIX to the letter is not needed, but it is of course satisfying knowing that your script can run fine on BSDs and other less common distributi…
-
comment
Comment #24275511
> Remember readable means that you can read and understand it Yes you are right, my usage of "readable" was probably wrong there. Maybe the point I was trying to make was less abou…
-
comment
Comment #24270038
The thing is when you restrict yourself to only what POSIX specifies you don't even have basic data structures, no array, no hash map not even local variables, and that often leads…
-
comment
Comment #24243971
-i is definitely not specificed by POSIX, but it supported on all those platforms with some small differences, for instance on OSX the backup extension (-i.bak) is not optional.
-
comment
Comment #23857548
Yep I can confirm intel cards are still an issue. I installed FreeBSD a week ago and gave up trying to enable Wi-Fi after an hour of struggle on a Thinkpad T490, didn't even get to…
-
comment
Comment #23813771
Yep that's exactly right :) ! To clarify my statement POSIX requires at least 8192 bytes for the pattern and hold space, and I chose to allow at most 8192 bytes here, which indeed …
-
comment
Comment #23813615
No concrete benchmarks no, I just timed a few scripts I had on hand and generated a bunch of others, and I saw compiled ones performed slightly faster than GNU and toybox sed, so n…
- story
-
comment
Comment #23177245
A Sed to C translator written in Sed, the objective being to be able to translate itself: https://github.com/lhoursquentin/sed-bin
-
comment
Comment #22938841
Really cool stuff, I've been working on being able to debug sed scripts as well by translating it to pseudo readable C[1], compiling the result and then using gdb to step in the sc…
-
comment
Comment #22389844
Regarding 4. it's an interesting point, and this actually exists, few people know that ksh93 (which was a big inspiration for bash and zsh) does not fork when it doesn't really nee…