The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
This is the 3rd version of the LALR(1) parsing. The first was an initial creation of Newt that i never released. The second version I never released either, but it worked - at least as well as this one did, which is to say fine until the input has errors.
The trouble with this is LALR(1) is incredibly convoluted. The algorithm is ridiculous. If you saw it the first thing you'd think is "oh my gosh there has to be an easier way, anything is better than this" - and normally you'd be right. The trouble is, mathematically you'd be wrong in this case. LR parsing is just *complicated* like that. The table generation - let's just say even an RDBMS would find it really tough.
The parser, for all that is shockingly simple, but unintelligible because the parse table is unintelligible by the time it's crunched. Traversing it is easy because there's a formula to it, but it still doesn't make sense, if that makes sense. =)
But all this means is as long as everything works as expected, it's great. But when you start getting errors in your input, all of the sudden you have to take over from the normal parsing algorithm, preserve its state, potentially modifying its state to account for the error(s), interrupt the parse to report the errors, and then continue, all while managing to keep the parse table synced with the input. This is convoluted in an LL(1) parser, much less a LALR(1) parser.
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.
There is a saying in Germany that you build your first house for your fiend, the second for your friend, and the third for you.
This must not only apply to house architecture, but also code architecture.
He can't, otherwise it is an abomination and not a game.
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
I have mentioned in the past I have had Jira landed on me, the general response from the learned crowd was 'Kill it, Kill it with Fire'. I didn't really follow that view as I used to have manage tests and documentation using a combo of Access, Excel & Word (fun times), Jira appeared to have it all in one place. However one thing struck me as weird is the 'prefered' way to get to tests is using the menu's Project -> Test -> Plan Test Cycle and then select from the appropriate tests down the side. Fine a little illogical but I can deal with it. This works if you have the 'frame' open, also if you execute a ticket with the Execute button you can execute a test outside of a test cycle, which will cause my Boss to meltdown...
It seems like it has been added to by different people, at different time, to do different things.
Now it can do various things some of which it was never meant to and it seems to be touted by people for various uses it can be be put to, like a Swiss Army Pen Knife, not the ideal tool but better than nothing.
Jira is a tool which is powerful and extensible.
That said, like any tool, it all depends on how you integrate it into your company, and how good the configured workflows match the real-life processes. If they do not match, as with any tool, you'll end up butthurt and crying - But that's not Jiras fault, but someone higherup ind the command chain not understanding how tools are supposed to help employees get work done effective and efficient rather than self-inflating a boss' ego about doing things the way he wants them done.
I only have a signature in order to let @DalekDave follow my posts.
I've ranted a bit before about Microsoft's pathetic excuse for an operating system. Window's only achievement is through marketing and "it's good enough." My customers do not and will not tolerate their machines crashing for inexplicable reasons... my assessment of Windows 10 on a good day is marginal, on an average day pathetic, and on a bad day - criminal. I'm being generous. For 25 years I've put up with "it must be a driver" bullchips, and as a professional by now MS should have fixed their exposure to this issue - practice safe drivers. Anyway, I rant and I want peace on earth and free healthcare for all....
Google "BSOD diagnosis" and you will get a pant load of sites that are nothing more than shills for "magic" s/w that does absolutely nothing. The next major category is anything beginning with "answers.microsoft... " I actually can hope that most of the posts are AI driven, but I'm not sure.
So for those of you who get into the muck to solve or at least accurately identify Windows 10 system issues - what are your preferred sites? What sites eat raw bits and crap ammo when they are done? tomshardware can have some traction from time to time.... crap, I feel an article forming.
There is nothing "free" in life. If you believe this, you believe in theft.