bool_pattern = ".*"
int_pattern = r"[+-]?(?:[0-9]|[0-9][0-9_]*[0-9])"
float_numeric_pattern = r"[+-]?(?:[0-9]\.?|[0-9][0-9_]*[0-9]\.?|(?:[0-9]|[0-9][0-9_]*[0-9])?\.(?:[0-9]|[0-9][0-9_]*[0-9]))(?:[eE][+-](?:[0-9]|[0-9][0-9_]*[0-9]))?"
float_pattern = r"[+-]?(?:(?:[0-9]\.?|[0-9][0-9_]*[0-9]\.?|(?:[0-9]|[0-9][0-9_]*[0-9])?\.(?:[0-9]|[0-9][0-9_]*[0-9]))(?:[eE][+-](?:[0-9]|[0-9][0-9_]*[0-9]))?|[iI][nN][fF](?:[iI][nN][iI][tT][yY])?|[nN][aA][nN])"
Discover gists
hello: hello.cpp | |
g++ -std=c++0x -o hello hello.cpp -lOpenCL |
blueprint: | |
name: Appliance Notifications & Actions | |
description: > | |
# 📳 Appliance Notifications & Actions | |
**Version: 2.0** | |
🤔 Watts your appliance up to, you're always in the know from start to finish!🛎️🔌💸 | |
JSON containing links to the all known PaperMC versions.
Note
This JSON is being updated manually.
If you want to always have the most actual paper-versions.json
, check out this generator: qing762/paper-version-links (dynamic JSON)
Kudos to @qing762
<!DOCTYPE html> | |
<html lang="en"> | |
<head> | |
<meta charset="UTF-8"> | |
<meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
<title>Custom Scrollbar Windows 95 Style</title> | |
<style> | |
body { | |
margin: 0; | |
font-family: Arial, sans-serif; |
<!DOCTYPE html> | |
<html lang="en"> | |
<head> | |
<meta charset="UTF-8"> | |
<meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
<title>Custom Scrollbar Windows 95 Style</title> | |
<style> | |
body { | |
margin: 0; | |
font-family: Arial, sans-serif; |
I wrote this answer on stackexchange, here: https://stackoverflow.com/posts/12597919/
It was wrongly deleted for containing "proprietary information" years later. I think that's bullshit so I am posting it here. Come at me.
Amazon is a SOA system with 100s of services (or so says Amazon Chief Technology Officer Werner Vogels). How do they handle build and release?
The big reason to do this is that LLDB has no ability to "follow-fork-mode child", in other words, a multi-process target that doesn't have a single-process mode (or, a bug that only manifests when in multi-process mode) is going to be difficult or impossible to debug, especially if you have to run the target over and over in order to make the bug manifest. If you have a repeatable bug, no big deal, break on the fork
from the parent process and attach to the child in a second lldb instance. Otherwise, read on.
Don't make the mistake of thinking you can just brew install gdb
. Currently this is version 10.2 and it's mostly broken, with at least two annoying bugs as of April 29th 2021, but the big one is https://sourceware.org/bugzilla/show_bug.cgi?id=24069
$ xcode-select install # install the XCode command-line tools