Carbon
cl-ppcre
Carbon | cl-ppcre | |
---|---|---|
18 | 13 | |
16,444 | 291 | |
- | 0.3% | |
9.3 | 3.7 | |
3 days ago | 9 days ago | |
PHP | Common Lisp | |
MIT License | BSD 2-clause "Simplified" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Carbon
-
PHP: check dates
Carbon is probably one of the most popular vendors to handle dates in PHP.
- Ask HN: What are some of the most elegant codebases in your favorite language?
-
Why was the Carbon library called that?
Official page, at the very bottom.
-
Calendar page displaying empty boxes and not days and numbers - $this->date
Let me start by referring you to PHP's DateTime implementation. There is a library called Carbon that uses this DateTime implementation and added almost all the methods you have (but better). So there really is no need to create your own just to be able to display Dutch names. That way to can get rid of the nasty "globals".
-
The Wonderful Carbon - Laravel
At first we go to https://carbon.nesbot.com/ Here we will see a lot of interesting information and go deeper into it See also https://github.com/briannesbitt/Carbon
-
Need help formatting week day and time
first of all, i think you should use Carbon library. it's available here: https://github.com/briannesbitt/carbon
- Any help will be greatly appreciated
-
Do you use a DateTime wrapper?
See: https://github.com/briannesbitt/Carbon/issues/1693
-
Creating a Neat DateTime Helper Function in PHP
Working with datetime in PHP could be a real pain if you don't take advantage of popular libraries like Carbon. It's all good until you have to convert dates provided on user input into another timezone (eg. UTC) and vice versa. Other example could be that you have to manage various input datetime formats, and sanitize them into a consistent one before saving it to database.
-
Carbon - Float Difference in Months Filtered
Be careful of floatDiffInMonths() which can gives you a lower result (number of months in A < number of months in B) for an interval having more days (number of days in A > number of days in B) due to the variable number of days in months (especially February). By default, we rely on the result of DateTime::diff which is sensitive to overflow. See issue #2264 for alternative calculations.
cl-ppcre
-
Compile time regular expression in C++
I've never used cl-ppcre myself, but its docs[1] claim that it provides compile-time regexes:
> CL-PPCRE uses compiler macros to pre-compile scanners at load time if possible. This happens if the compiler can determine that the regular expression (no matter if it's a string or an S-expression) is constant at compile time and is intended to save the time for creating scanners at execution time (probably creating the same scanner over and over in a loop).
[1]: https://edicl.github.io/cl-ppcre/
- Ask HN: What are some of the most elegant codebases in your favorite language?
-
sbcl and Let Over Lambda
A few weeks back Xach recommended cl-ppcre which i found educational.
-
-🎄- 2022 Day 1 Solutions -🎄-
For simple string processing, there are some functions in the language, that you can find listed here (for string-specific functions) and here (for more generic sequence-handling functions). For anything involving regular expressions, cl-ppcre is the way, in particular the split and register-groups-bind functions.
-
The unreasonable effectiveness of f-strings and re.VERBOSE
I must have a serious bug in my writing about this, because this was never about regex engines -- it's about literals and domain-specific sublanguages in general. Composing DSL programs by string concatenation is such a famous source of security bugs you see it in top-10 lists. I linked to the very similar example of a PEG parsing DSL.
But any regex engine that can work with a parse tree shows the same principle, e.g. https://edicl.github.io/cl-ppcre/#create-scanner2
-
Adding Space to subst function
Take a look at - https://github.com/edicl/cl-ppcre
-
Common Lisp ASDF maintainer considers resignation
And here's what I believe represents the reality of the situation... Stas was indeed tired of ASDF's changes. Now the nature of what changes to make is a matter of judgement of course, but in this case (I'm thinking of SBCL's bug report request to update ASDF: https://bugs.launchpad.net/sbcl/+bug/1826074), it would be a different matter altogether if the discussion was centered on how best to make the new ASDF work with SBCL, but the thread reads to me like a man who had to put up with too much breakage for the upteenth time. Now, if (for the sake of argument :D) the change was of the necessary kind -- think hardware changes or security issues -- I can still see myself feeling wronged, it's human to do so. Because I don't trust ASDF anymore or I feel as if they (or other people at each step of the process) have not shared enough of the burden. But from the discussions I have read (https://github.com/edicl/cl-ppcre/pull/30) what the ASDF maintainers want to change does not seem unreasonable and they are willing to share the burden. But let us say it's truly a 50/50 deadlock. Well then Linus is right, show us the code, who dares wins. And Stas certainly has enough on his plate. But that's why we must cooperate. You don't have to be a diplomat to know the difference when two people want to work together and when one party wants out. And this setting makes more sense when you read (https://bugs.launchpad.net/sbcl/+bug/1823442) where Stas honestly states he wants nothing more to do with ASDF. I don't think it's unreasonable to surmise there's a bit more going on here than plainly technical issues.
-
Stas has alienated long-time ASDF maintainer Robert Goldman
Could you just direct me to some existing discussions, in order to save time? I already read this one.
-
#"<your literal interpretation here>" (regular expression literals)
I plan to use the regular expressions with a cl-ppcre wrapper, also emulating various clojure regular expression operations. Similar to re21, which doesn't quite support the operations in the way I'd like (or match the clojure operations), and whose regular expression literal syntax is "#//".
What are some alternatives?
Moment.php - Parse, validate, manipulate, and display dates in PHP w/ i18n support. Inspired by moment.js
sbcl - Mirror of Steel Bank Common Lisp (SBCL)'s official repository
Chronos - A standalone DateTime library originally based off of Carbon
one-more-re-nightmare - A fast regular expression compiler in Common Lisp
Yasumi - The easy PHP Library for calculating holidays
aoc2022
CalendR - The missing PHP 5.3+ calendar management library.
advents-of-code - 🎄🎁 Solutions for the yearly advent of code challenges
ExpressiveDate - A fluent extension to PHPs DateTime class.
advent-of-code-2022 - back to rust, except i'll use libs where it makes sense
Duration for PHP - Working with durations made easy
advent-of-code - All my advent of code projects