Oh dear. I'm responsible for at least three of these. (Bash is a moving target...)
Function context specifically means function, not any other nested call context:
$ echo "$(local ll=42; echo $ll)" bash: local: can only be used in a function
Which is kind of annoying. I want to use generic infrastructure for this.
Ok, function lifetime rules: right now sh_function 'scratch' instances store the parsed function blocks, which get cleared/freed when an executable chunk goes out of scope. (So they live for the lifetime of loops, but when you exit the loop it goes away.) This means that command line and shell script parsing work the same way, with the same lifetime rules. Stuff you type at the $ prompt gets freed as soon as it's no longer needed, so why shouldn't stuff read from shell script input?
Declaring a function kind of needs to instantiate a new sh_function instance (to store the sh_pipeline list with parsed command pipelines), but it doesn't put a name into the function namespace (if you call this name as a command, it's a shell function instead of searching the $PATH) until the function statement is _executed_. If you have a function in another function, the outer function declaration is executed but the inner one doesn't get executed until you _call_ the function...
The parsing needs to create discrete function instances, with separate sh_pipeline lists with their own allocation lifetime. If they're not assigned to a function name yet, they live within the enclosing function, but when assigned to a function name they can live beyond the original function's lifetime.
$ chicken() { potato() { hello() { echo one; }; echo two; }; echo three; }
$ chicken
three
$ hello
bash: hello: command not found
$ potato
two
$ hello
one
$ unset -f potato
$ hello
one
$ potato
bash: potato: command not found
$ chicken
three
$ potato
two
Sigh: they need to be reference counted. And I need to treat function bodies a bit like HERE documents, where there's an array of them and the zeroth entry is just the standard plumbing. In an sh_pipeline the first sh_arg entry is the command line, and the later ones are HERE documents, with one line per entry in arg->v[]. Now I need an array of sh_pipeline entries, one per function, nesting arbitrarily deep.
The question is, how do I associate the function() declaration in question with the relevant pipeline[] entry? For HERE documents I just count along as I go, with the consumer iterating through the same way the parser did and the count matching. (Either way, this is the third HERE document...) I guess functions can do that too? That's a lot to rewrite...
Having pl2str spit this back _out_ for marshalling into nommu subshell context is going to suck. I haven't even implemented support for HERE documents in that yet, now I need pl2str to accept an _array_ of pipelines so it can handle nested function declarations...
December 27, 2020
Sigh. Japan's going back into lockdown on January 3, if I'm flying back I might have to do it before then. (Jeff thinks I shouldn't, he can't make it back there before then so I'd be alone in the Hello Office. Mike and Arakawa and so on all have their own offices on the far side of Shibuya so don't get to Asakusa much.)
I can't say I'm surprised. Half my worry about returning was that the USA's covid response was still a gigantic shitshow. And once a vaccine existed, Japan was likely to start requiring vaccination as a condition of return. But Japan apparently has the new UK strain which has driven their R value above one despite near-universal masking. (Yeah with some dicknosing when I was there, but it's actually an interesting social signal, you can immediately tell "this guy is an asshole" at a _glance_. Saves time. I reminded Fade to order me some of the "it goes over your nose" masks, but will they get here in time if I'm leaving? Am I leaving, or am I stuck here again through... what, August? No idea. Of course 2021 is as full of uncertainty as 2020, it's gonna be like this until enough Boomers die for the survivors to dismantle capitalism and start addressing climate change.)
Twitter has now emailed me 7 times since tuesday finding more of basically the same tweet, each time sending the same form letter saying my account has been freshly locked (implying that locking it on tuesday didn't count?) and ignoring the fact I haven't been able to post to it since October 2019 because I'm not giving them my phone number. (Not to mention ignoring the validity of the political position, but it's a private platform and they can require all posts to be in sanskrit if they want to.) I'm pretty sure Twitter is trying to do the "good people on both sides" thing by declaring complaints about plutocracy equally offensive to the racist kids-in-cages nazi brigades they ignored forever. If twitter has to take out one, they're 100% going to take out the other because there can't POSSIBLY be a right side to this, can there? Not according to twitter there can't.
Is it any wonder why I argue for changing the law so offensive accumulations of capital become a capital offense (guilloting the billionaires with full due process of law as a proper symbolic repudiation and statement of what we as a society will no longer allow, just like kings centuries ago) when lawyers are literally saying the GOP just "came close to destroying democracy in America. Another term would have done it." The problem isn't a political party: the crazy 27% ready to go full fascist at the drop of the hat have always been there. (Given the amount of child abuse in this country, it's not really surprising some people grow up wanting to hurt and dominate.)
The part that's new is Reagan's tax cuts empowering greedy plutocrats happy to push children into meat grinders for money, plus the senile Boomers enabling them. Plutocracy in this country committed genocide against the native americans and kidnapped millions of people into slavery for financial gain _before_ causing a civil war where poor southerners were convinced to do "Pickett's Charge" in defense of the plantation owners. Fox News was literally founded by Richard Nixon's speechwriter with the aim of making sure another Watergate couldn't happen because any level of malfeasance could be neutralized by the GOP's version of Pravda.
Lobbying merely to TAX billionaires is not a proportionate response to this problem, but if taxing billionaires out of existence is all we get, "out of existence" is the important part. Covid is killing more people each day than 9/11 did and has already killed more US citizens than World War II did, and "long covid" aside doctors strongly suspect it has a years-later recurrence like shingles with chicken pox or post-polio syndrome so getting it even at a young age could be really bad, and the only reason the USA is NOT handling it like Australia (let alone New Zealand or Taiwan) is because the plutocrats in charge of the USA don't want that, they're profiting from the pandemic. Meanwhile covid pushes "kids in cages" and puerto rico recovery and the west coast wildfires out of the news...
Of course plutocracy brought on by late stage capitalism is not limited to any one country. Here it is in canada.
Defunding the police: wage theft is three times as big as property theft, and most military spending is wasted too (defense contractors pocketing checks and delivering garbage, it's a make-work program like Keynes' bottles of cash buried in old coal mines, just an excuse to make basic income look like a job to prop up the idea of capitalism long after it stopped making sense). To plutocrats and their GOP servants constant lying is automatic as breathing. They have entire think tanks and PR firms to smear their critics. Boomers gonna boom and Boomer Media continues to suck. Christianity is killing people, as usual. Of course Biden's going to pardon nixon again, but may do so passively. (Just ignore everything for 4 years.)
December 26, 2020
I've been trying to get glibc's ldd script to work, and I'm up to the point where it's making a function call, and ok I need to implement shell functions. And it turns out it's harder than it looks, because I've been conflating "parse stack" with "call stack". When you use "source file.sh" that increases the PARSE stack depth, but is not a function call. Bash's parse stack is actually kind of sad, because you can't have function definitions or if/else/fi blocks straddle across "source". (I was treating them as C #includes, but no. They gratuitously reset the parsing context. Kinda needlessly if you ask me but I'm sure there's some shell limitation from 1973 encysted within posix somewhere demanding this be how it be done forevermore...)
The function stack includes local variables, which the call stack does NOT participate in:
$ bash -c 'local abc=123; echo $abc'
bash: line 0: local: can only be used in a function
$ echo local abc=123 > test2
$ bash -c 'source test2'
test2: line 1: local: can only be used in a function
$ bash -c 'chicken() { source test2;echo $abc;}; chicken'
123
(I don't believe I've ever actually seen "the funky chicken" danced, but when asked for a function name while sleep deprived it's sort of my default with shell functions for some reason. They're inherently kinda funky...)
Meanwhile, function declarations are statements that assign a function to a function name, which appears to be a global namespace that persists past function lifetimes but parsing a function is not the same as ASSIGNING a function:
$ cat chicken.sh
#!/bin/bash
chicken() { banana() { echo abc; }; banana; }
banana
chicken
banana
$ bash chicken.sh
chicken.sh: line 4: banana: command not found
abc
abc
And the namespace lifetime rules are tricksy:
$ potato() {
> banana() { echo one; }; banana;
> banana() { echo two; }; banana;
> }; potato; potato
one
two
one
two
But it's not NOT assigning a function either:
$ cat test3.sh
#!/bin/bash
chicken() {
$1 () { echo blort; }
}
chicken potato
potato
$ bash test3.sh
test3.sh: line 4: `$1': not a valid identifier
test3.sh: line 8: potato: command not found
Oh, and function bodies are "compound commands", which isn't just { } but also:
$ echo $$ $BASHPID; chicken() (echo now $$ $BASHPID); chicken 5112 5112 now 5112 5528
Yes, it's spawning a subshell (even thought $$ always gives the top level shell's pid, not the current subshell process). The man page says you can do it for [[ ]] and ((math)) too: I don't know why.
And having toysh pretend to be bash is because things like $BASHPID say "bash" in the name. They could have had $PID be the non-broken $$ replacement, but no.
December 25, 2020
Christmas day. AFK.
December 24, 2020
Twitter emailed me again today:
Hi @landley, Your account, @landley has been locked for violating the Twitter Rules. Specifically for: Violating our rules against abuse and harassment. You may not engage in the targeted harassment of someone, or incite other people to do so. This includes wishing or hoping that someone experiences physical harm.
I look forward to the end of late stage capitalism. Guillotine the billionaires.
Please note that repeated violations may lead to a permanent suspension of your account. Proceed to Twitter now to fix the issue with your account.
Go to Twitter
I still haven't been able to post to twitter for over a year because after the first 12 hour suspension (for another "guillotine the billionaires" tweet getting retweeted and going mildly viral) they wouldn't let me back in without providing a phone number. So everything they're responding to is at least a year old.
The day before yesterday twitter sent me an identical form letter pointing at two different year-old tweets (out of the literally hundreds of repeats of that sentiment I tweeted (going back to 2012). So as far as they're concerned A) I haven't posted in a year, B) my account's been "locked" for days, but C) they're gonna lock it AGAIN for expressions of a common repeated sentiment.
My guess is the sentiment is starting to gain traction elsewhere and somebody's getting nervous. There's a twitter hashtag, and one on etsy and on instagram, and...
Merry christmas, twitter. You're still bad at being twitter.