Hi,
On Mon, Jan 22, 2024 at 08:11:42PM +, ruivlea wrote:
> After sbase commits:
> - 270ca025ce236885e3177cd7acfd2cfbdf6e36a5
> expr: don't evaluate matched substr as a number
> - e50d533d598dbe284e225e2ee52ed5f76a6e6f6a
> expr: treat expressions as strs until evaluation
>
> I fail to buil
Hello,
After sbase commits:
- 270ca025ce236885e3177cd7acfd2cfbdf6e36a5
expr: don't evaluate matched substr as a number
- e50d533d598dbe284e225e2ee52ed5f76a6e6f6a
expr: treat expressions as strs until evaluation
I fail to build linux using sbase
due to expr segmentation fault:
Linux Makefile
> I am personally not opposed to using yacc. Yeah I like hand-rolled
> recursive descent parsers are cool but yacc is a standard tool that
> most people are familiar with.
>
> Roberto, what do you think?
I agree with you. I think yacc is a suckless tool, and I am sure we will
have to use it for
On Thu, Nov 06, 2014 at 09:00:32PM -0800, Evan Gates wrote:
> I saw in sbase's TODO that expr had been imported from OpenBSD and
> needed "replacing or cleaning up." I decided to give it a try with
> yacc. It turned out very different from what I expected due to the
> need to convert between string
I saw in sbase's TODO that expr had been imported from OpenBSD and
needed "replacing or cleaning up." I decided to give it a try with
yacc. It turned out very different from what I expected due to the
need to convert between strings and numbers. It's about 3.5x smaller
than the existing implementat
