|
Since nobody else has, I thought I'd throw it out there.
Wishing you all success, happiness, and PHB freedom for the forthcoming year - may your bugs be trivial, your compilations clean, and your code self documented!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Happy new year for everyone from me too...
I whish you that the best of 2019 is the worst of 2020.
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.
|
|
|
|
|
Happy New Year to all! ![Beer | [beer]](https://www.codeproject.com/script/Forums/Images/beer.gif)
|
|
|
|
|
Very Merry Christmas And Happy New Year 2020, You too. 
|
|
|
|
|
Well, it is still a little early here across the pond, but let me wish one and all a happy, healthy and prosperous new year! ![Java | [Coffee]](https://codeproject.freetls.fastly.net/script/Forums/Images/coffee.gif)
|
|
|
|
|
Happy New Year 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
OriginalGriff wrote: code self documented
It's much easier to enjoy the favor of both friend and foe, and not give a damn who's who. -- Lon Milo DuQuette
|
|
|
|
|
Happy New Year to y'll as well!
Did a little mechanic work today.
Put a rear end in a recliner!
JaxCoder.com
|
|
|
|
|
Adding my $0.02:
Happy New Year y'all!!
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
Yes happy new year to you all!
|
|
|
|
|
A happy new year to all.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Happy New Year to you too!
|
|
|
|
|
HNYTYA (20 chars)
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
A euphony port alleyway!
Another yuppy yellow A.A.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Happy new year, OG! Good health and happiness!
/ravi
|
|
|
|
|
Happy new year!
I hope everyone’s had a chance to get some R&R over the break (refactoring and rewriting in my case. Ah, the peace and quiet of an empty office!)
cheers
Chris Maunder
|
|
|
|
|
Happy new year to everyone from me too.
If you are not criticized, you may not be doing much.
|
|
|
|
|
I wish for a very happy and fulfilling new year for everyone.
|
|
|
|
|
|
Garfield is a real influencer 
|
|
|
|
|
I think I can parse anything with Parsley. I'm pretty confident in it at this point, despite its immaturity. It still is cranky because I'm not finished with it, but now all of the foundation is there.
It can parse C#. That's a tall order. With a little work (mostly lexer support for significant vs insignificant whitespace) I could parse Python. That would be easier given that lexer support because it's not so ambiguous.
I also never had to break from an LL(1) parser algorithm except in my hand-rolled routines.
Parsley will eventually be LL(k), i think. Or maybe LL(*). It depends on how big the code that gets generated winds up being.
It *did* generate a 1.3MB source file, but unlike the 800k source file i got from ANTLR for parsing C#6 (which didn't work) you can follow it in a debugger pretty easily, and Parsley actually parses C#, or at least the subset that is useful to me, though I'm confident by now i could pretty easily parse the rest of it too. I just don't have anywhere in the CodeDOM to put what i'd parse! CodeDOM knows nothing of things like anonymous methods or lambda expressions or LINQ
This is just so cool. I've been wanting to do this for a long time. (Parse C# with one of my parser generators that is)
I never thought it would wind up being a recursive descent parser generator that did it. I wrote it that way for a lark, but it worked out really well.
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.
|
|
|
|
|
Wow.. nothing gotta stop you now! 
|
|
|
|
|
I knew I'd nail it eventually. This is what I wrote Parsley for - to parse Slang.
It's bigger than a hand generated parser would be by a fair bit, but also my hand rolled parser barely did any error checking, and what it did report was dodgy.
Adding: I keep forgetting it's the new year. Happy new year!
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.
|
|
|
|
|
Yes, error checking isn't usually added until it starts to "work", so it can cause upheaval. But it's so much easier to debug if the parser--and also what is basically an interpreter, for me--can pinpoint where they failed, with a message that makes sense. And keep going, so that you don't have to uncover one problem at a time.
|
|
|
|
|
Greg Utas wrote: And keep going, so that you don't have to uncover one problem at a time.
That's one thing I haven't figured out how to do in recursive descent parsing - error recovery.
My PCK project does it but not this. Maybe down the road.
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.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
