with a for loop maybe
I know that we have a test for this, and that it passed
Should we place that in the request somewhere?
When the content-data is set to application/json should we place the above as :parsed-body instead of using $_POST?
I would also say that. I think it's ok to use the native PHP functions for most of the common things such as strlen or similar.
But well, in case anyone find/does some interesting functions for phel that might get an additional advantage of having them in phel and not in native-php, then feel free and welcome to create a PR with it :)
But well, in case anyone find/does some interesting functions for phel that might get an additional advantage of having them in phel and not in native-php, then feel free and welcome to create a PR with it :)
The source code is here: https://github.com/mabasic/mariobasic-n7
Let me know what you think :)
There are some bugs that I need to polish like mobile experience etc.
Adding re-seq phel function 👉 phel-lang/phel-lang#259
Returns a sequence of successive matches of pattern in string.
@jenshaase Regarding PHP interop (calling phel from php). I haven't tested that part yet, but have you seen this article https://www.simonholywell.com/post/2016/10/importing-and-aliasing-php-functions/. I remember discussing something about not being able to call phel functions directly from php...
oh it doesn't have permissive license :(
anyway congratulations for the website :)
now I use calva instead of phel extension. it gives bad coloring and thinks my core is wrong but without paredit coding lisp is hard
@metehan The one thing that was really helpful when coding Phel is bracket matching in vscode. That is basically all that one would need. After some time you get used to working with brackets. The extension could provide symbols which would show functions and variables defined in a document. That would be helpful, but I managed without it.
@metehan Regarding the license, I will look into it at some point in the future. I'm currently busy with other projects, so I will have to circle back to this.
1 reply
@metehan ...Phel is bracket matching in vscode. That is basically all that one would need...
it's totally not "all one would need" :) you came from php as your website indicates. I can't imagine an effective coding experience without paredit on a lisp language. You should install calva paredit. after you try it then there is no way back from lisp family languages ;)
thank you Jens for the sample
Just published a 100 loc Phel backend for the canonical "guestbook" web-example. Thank you @mabasic for the inspiration.
Hi everybody. I just want to inform you that I'm working on a pretty big change regarding Phel's data structures. I will replace the existing data structure with new persistent data structures similar to Clojure's data structures. This will break a few things in the next version, but I think it's worth it. If you want you can have a sneak peek by looking a the Pull Request: phel-lang/phel-lang#244
1 reply
@mabasic project added. At the moment I am using your splendid JSON library to performantly exchange data between cljs<->phel. But with JSON, sending data of the form [:key1 {:key2 2} :key3] is tricky. I wonder whether in the new Pull Request there exists some kind of "read-string" function which would perfectly fit reading a String of cljs/EDN data into the new Phel data structures. One would lose performance by sending a String instead of JSON, but it would be very convenient.