|
Looks like it might be above my reading level.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
The "Three Laws of Robotics" suggested by Isaac Asimov is now revealed to have an assumption id est said laws can be programmed w/o error. Other than human error now of course we know the mode of said programming id est LLM results in occasional hallucinations.
|
|
|
|
|
I had to reinstall SQL Server. When I rebooted, window automagically applied a Windows update. Now, my Taskbar in is TRANSPARENT!!!
I quick Google search found this[^]
You really havfe to wonder - does anyone at MS actually test their changes???
In theory, theory and practice are the same. But in practice, they never are.”
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
|
|
|
|
|
So did uninstalling the update fix it?
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
I didn't try. I don't have 2 hours to reboot
In theory, theory and practice are the same. But in practice, they never are.”
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
|
|
|
|
|
On the second page of your MSDN Forum link, it says the explorer patcher causes this issue. Just update your explorer patcher will fix the transparent issue.
|
|
|
|
|
Gawd, is that the root reason?
I've always been so against these third-party apps that try to sneak into Windows to replace default behavior. This is exactly why.
|
|
|
|
|
I've been on a Drum and Bass kick lately.
Especially atmospheric, jazzy stuff. I forgot how great it is to code to.
It's motivating without being too engaging or otherwise distracting.
Urban Flavour - Modern Jazz Drum n Bass (1998) - YouTube[^]
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Nice, I like it.
|
|
|
|
|
Very cool. I find that I'm inspired and motivated when I code by listening to electronic progressive and trance.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Early 1990's. I always like the beat of this. Jimi Jamison's vocal's.
https://www.youtube.com/watch?v=HcmFCeaDxGs
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Not bad. Rather Pleasant. I sometimes code to that 40 Hz binaural stuff.
|
|
|
|
|
Student: I am getting Syntax Error in my code.
Teacher: Show me your code.
Student: Here it is:
#include<iostream>
using namespace std;
void main()
{
cout << "Syntax Error" << endl;
}
Teacher: Grrrrrr...
Where's my coat?
|
|
|
|
|
It's been years I've written as much as a Hello World in C++; would all modern parsers be 100% okay with the fact that there's no space between the #include and the following <iostream>?
|
|
|
|
|
Just tried it with a 20 year old borland c++ compiler and it accepts
#include<vcl.h>
#include"Mainwindow.h"
|
|
|
|
|
Now throw Resharper at it. It'll bitch and complain until you fix it or disable the check.
I like R# for some of its suggestions, but sometimes it goes overboard and annoys me to no end.
|
|
|
|
|
You can write an entire C/C++ program on a single line, which is why all those punctuation characters are so important.
|
|
|
|
|
Richard MacCutchan wrote: You can write an entire some C/C++ programs on a single line,
FTFY
Sometimes you cannot:
#define A "Hello world!\n"
int main(int argc, char** argv)
{
printf (A);
return 0;
}
When discussion comes to blanks and line endings I always remember a funny picture from an old book.
Mircea
|
|
|
|
|
Well technically, the #define is not part of the program, is it?
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
I would say that "technically", the preprocesor is part of the language (preprocessor is defined in K&R), hence #define is part of the program.
However, I'm not going to start a war here about such minutia, and specially not with such nice people.
Mircea
|
|
|
|
|
Would you care to discuss tabs v. spaces?
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
*Python has entered the chat*
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
If it's not, then neither is #include
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Completely agree.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Correct.
Pre-processor directives are resolved before the code reaches the actual C/C++ compiler.
The output of whatever pre-processor(s) you use is the actual code.
Or -- as I do -- use a C/C++ pre-processor to resolve directives I put in C# and pass the result to the C# compiler.
But you know that.
|
|
|
|