So my local hobby shop posted a list of sale items (but they still don't have a real website) So was googling to figure out what was on sale. Scientific Notation for an advertised top speed is technically correct, but it amused me. [link](https://www.amazon.com/ARRMA-VORTEKS-BRUSHLESS-Included-ARA4305V4T3/dp/B0DN46V9JV/ref=sr_1_10?crid=2SOR9MDNACWW8&dib=eyJ2IjoiMSJ9.sm3EpdFSZBmS4oJCGPdDnKGTuQ6HxEdbDC9Ya90to4sbBEZpXurY81KKeOVMSZkiL8C7188SlbN0D5EkZRaWqNMJB4CfrN_A5eMzmOA9PArxtl15bL_4vD9aYA7OlP6TBtBh6O0xm0GNrnMrKFFI-Ku9oeVO4LOXbapO8BOiIH9z0IgB2uLpPWiGYZ6NAnFXqQq25wF4ZmtWKOQWs2I2QezfjMVeHD_qkWs8qD6IcRVlmOO-KGNW04zojzt3JdWfAoRpvZqZpoMBjxV4kWyt2PxZWaRKh6b4m_CzNaLFSQk.ugmPP51cEkU2A5g1PfbQtEPcAXeekF
zerj
u/zerj
Kueng and Thao sentenced to 3 years in federal case.
cnn.com/2022/07/27/us/tou-thao-kueng-george-f...So I noticed the Shaw's website specifically asks if your BMI is over 40 as a qualifying criteria. However the state just says you need to be classified as 'Overweight' per the CDC (BMI = 25). Is the Shaw's website instructions out of date? or am I in for a surprise when I show up for an appointment in a few days? Especially as they mention wanting 'proof' in their confirmation email.
So this is perhaps a stupid question, but while browsing I noticed that VOO lists an expense ratio of 0.03, and the Admiral version VFIAX actually has a slightly higher expense ratio of 0.04. Did I miss some news here? I thought the whole point of Admiral was lower costs
So way back in the 80s one of the first editors I used was Microsoft Edit, and back then cut/paste was shift-insert/shift-delete. Surprisingly just about every edit window still supports that and it still seems like the most universal command (certainly more so than ctrl-c/ctrl-v or emacs's c-w/m-y)
I'm working on a new server and now about 30% of the time shift-insert inserts a "^@" instead of the paste buffer I would expect. It's starting to get on my nerves and probably something in my .emacs profile doesn't quite agree with the version of emacs on this server, or maybe even the vnc software getting in the way. Anyone run into this one before?
So cleaning out an old hard drive and found a text file with examples I had seen while I was consulting. The file was from 2002 so hopefully all this code has been retired.
-
#defines instead of actual numbers in code are generally a good idea but this is pushing it.
#define SCC_ZERO 0 #define SCC_ONE1 1 #define SCC_8000 0x8000 #define SCC_C0FF 0xC0FF
-
More from the same code here implying that the compiler can distinguish between 0x0000 and 0x00000000 .
#define BP_ZERO16 0x0000 #define BP_ZERO32 0x00000000
-
The original code had almost all 26 letters of the alphabet in use but I think you get the point. Now I'm envisioning this started with
So I like to keep my code warning free. The issue for me is usually I'm stuck with incorporating libraries that I didn't write. I've been seeing this warning for a couple weeks coming out of an industry standard library:
.../sys_datatypes/sc_lv_base.h: In member function ‘sc_dt::sc_logic_value_t sc_dt::sc_lv_base::get_bit(int) const’: .../sysc/datatypes/bit/sc_lv_base.h:310: warning: suggest parentheses around arithmetic in operand of ‘|’
So finally got around to looking at the line in question:
return sc_logic_value_t(
m_data[wi] >> bi & SC_DIGIT_ONE | m_ctrl[wi] >> bi << 1 & SC_DIGIT_TWO );
Just because you memorized the order of operations doe
So I was debugging a segfault in a predecessors C code. I found this:
void func(int x, int y, int z){
int arr[y];
......
}
Well I guess I'm showing my age here as I would never have though this is actually legal. Looks like it was added to the C99 standard. Still not sure why you would ever do this vs a more explicit allocation where you can check to see that the allocation was successful. I actually get worried seeing more than ~128 bytes of stack variable in a function, but that's my quirk due to years of embedded programming, and always being short on memory.
The addition of the tool cabinet is a big improvement over the Alpha build. However it seems to break the ability to hide a small base somewhere. Now whenever your running around and see "Building Blocked" flash you know there is a base nearby long before you see it.
Would it be better to remove the status and only find out you are blocked by trying to place something? Maybe with some exception when your tool cabinet is destroyed/deauthorized?

