|
On a side note, I just greatly improved app performance (with like 5-6 seconds!) by replacing:
using (var client = new HttpClient()) With:
using (var client = new httpClientFactory.Create()) 
The client is used to get the status of some 100 items in separate GET requests.
I did it async already, but it still took 5 to 6 seconds, back to some 500 ms now 
You know how it feels so I thought I'd let you share in my joy
|
|
|
|
|
YAY!
Also bless HTTP pipelining
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
I just greatly improved my app performance by fixing a bug.
It was taking infinite time to complete.
Now i don't know how fast it is, but it's infinitely faster now.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
Thread.Sleep(double.PositiveInfinity);
Good to hear your app went from infinite time to less infinite time though 
|
|
|
|
|
Well I'll probably have to order the Dragon Book after all to sort out the error recovery in the LALR(1) parser but still, as it is this whole project is just the bees knees.
I'm happy with it. I can author and test grammars, and generate code all from my little gui, which is basically like notepad++ with tabs and some build macros + a tester sub-app
Woot.
But now that i'm happy with it I don't quite know what to do with myself.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
honey the codewitch wrote: sort out the error recovery
throw new AccessViolationException();
|
|
|
|
|
LOL!
the whole point is to NOT throw errors, but rather, return error nodes in the parse tree when the parser encounters errors, and to continue parsing.
you know how visual studio will show multiple syntax errors in your code at once?
this is how it does it. Its parser has to continue even when it finds syntax errors.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
errorNodes.Add(new ErrorNode($"Access violation at address {Guid.NewGuid()} in module 'Pck' Read of address 00000004"));
As you can see, I've really got a solution for everything
|
|
|
|
|
You really like access violations.
I know some shrinks that would have a field day with that.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
Pull out a bottom card and watch them all crash down.
Just kidding, but figuratively you should try something like that. Try some unexpected inputs and see how it handles the perturbation.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
modified 18-Aug-19 19:03pm.
|
|
|
|
|
That's rather the point
I even have a test where it takes erroneus inputs and even with errors its expected to be able to complete the parse *AND* reconstruct the entire document based on the nodes therein. I compare that reconstruction with the original input so it's very demanding in terms of precision. Everything has to be reported even in worst case scenarios.
The LALR(1) parser does not pass these tests, but the LL(1) parser does.
Still, I'm satisfied enough with it for now. The error handling in the LALR(1) parser is going to be dodgy until i get my copy of the dragon book and can look at what they recommend.
This isn't standard error handling. This is being able to handle a situation where the input does not meet the expected format, and yet you have to continue parsing. It can be challenging.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
honey the codewitch wrote: This isn't standard error handling. This is being able to handle a situation where the input does not meet the expected
In the automation world we say, you are so good as your "home run".
To program the "automatic mode" step chain is the easy part, no matter how exigent is the process. The most difficult part is mostly the "home run" (bring the machine, production line back to the "ready to start" or "ready to continue" after an error)
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
pretty much exactly this.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
This could be a valuable tip/trick or article. cheers, Bill
«Where is the Life we have lost in living? Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?» T. S. Elliot
|
|
|
|
|
Well, basically there are a whole bunch of security holes in software that we all write where we do not parse inputs. And to top that off, even if you don't have an internet connection, you can still mess up parsing enough to crash your own computer. I have done it so I know it's possible. There was even an old way for mac users to secure their passwords relying on bad parsing, they would put control-alt-delete in their password which would cause a PC using hacker to reboot their computer if they tried to use the password.
|
|
|
|
|
AnotherKen wrote: software that we all write where we do not parse inputs
That's the point, this one DOES parse the input, it's the whole point of the software.
I'm assuming this was written in C++.
Getting an AccessViolation in C# like that requires an advanced level of incompetency.
But the parsing would basically just be "Line starts with H? Get first eight characters, then get the next 11, then 11 after that, etc. until you're out of characters."
If the line starts with a V it's a bit trickier since the length of the groups depends upon a value in the nearest H line above it, but still not very difficult.
It should be really easy to check if you've got enough characters for both lines.
You always know how many characters you'd expect and how many you've got left.
This isn't rocket science, especially since it's just a service doing "get input, parse input, do something with input", no system level functionality 
|
|
|
|
|
So ... does anyone know how to transfer the panes layout from one to the other? I'd really like them both the same, but it's a frustrating process getting the right, and although I can save the layouts, I can't find where they are saved to copy them to the new machine ... and the VS settings dialog is getting less helpful with each iteration.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Ok, I get this question a lot, so here's what you do...
Take both machines and place them next to each other.
Then, with all the strength you can muster, slam them together really hard so that data from one machine can jump into the other.
Be careful though, if you slam too hard, or in a wrong angle, or even just time it wrong, your machines will break and you'll lose all your data.
It's tricky but it can be done.
If really all you want is to transfer the screen layout, simply unplug your monitor and plug it into the other machine while leaving your monitor in front of the machine that you want to copy.
Hope this helps
|
|
|
|
|
Damn! I need to transfer from the desktop to the surface and you method only works the other way.
I tried feeding the surface into the DVD slot, but the door wouldn't close. Help!
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: but the door wouldn't close
Just push harder
|
|
|
|
|
|
Salt-N-Pepa was always one to rap about modern IT problems.
Their lyrics have helped a generation of IT nerds and helped shape the modern IT landscape
|
|
|
|
|
A little dwarf just walked around a corner, saw you, threw a little axe at you (which missed), cursed, and ran away.
You are in the Hall of the Mountain King, with passages off in all directions.
There is a little axe here.
A huge green fierce snake bars the way!
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
