The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
that you don't have to do any quantifiable work anymore?
yes, but when the slippage occurs even though you can blame the dev you have to deliver the news, and justify why they failed.
actually worst PM gig I had boss wanted me (on a late delivery) to tell the client X. Problem was it would mean lying to their faces.
I said, "no."
He said, "OK, expect your resignation letter ASAP." (I think expecting me to back down.)
2 minutes later he had my resignation.
Stupid pricks made me serve my notice. (about 2 weeks (4 weeks less leave), arrive late, long lunch, leave early (usually 5 minutes after getting back from lunch) - punctuated by ms solitair etc.) hmmm, next discussion topic
ah, well ANTLR is pretty well covered territory for me. In fact I started experimenting with a similar technology that ANTLR uses for its "parse tables" (actually state machines) in my projects though I may not go with it as I think I found a better way to do LL(k)
In the end, I'm making a universal LL generator. LL parsing is the easiest to use, but currently the hardest to design grammars for because LL(1) is limited, and LL(k) is complicated and traditionally memory intensive, while LL(*) is expensive.
ANTLR4 uses a variant of LL(k) called LL regular (I think?)
I'm making my own "strong" LL(k) using a technique that i think is somewhat similar to this one: The PREDICT-k Function[^]
So basically I'm making my own ANTLR but eventually I intend to extend it to LL(*) - which I've already implemented part of, and I need to finish my LL(k) 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.
Last Visit: 14-Dec-19 19:15 Last Update: 14-Dec-19 19:15