|
W∴ Balboos wrote: start eating a lot of beans
Mexican jumping beans? 
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
What a big beautiful wall sail! 
Sadly, it seems like a huge waste of taxpayer money. Nevermind, I forgot...Mexico's paying for it right?
"Go forth into the source" - Neal Morse
|
|
|
|
|
The section of wall was under construction at the time, with concrete anchors being put in place. But the strong winds blew the panels over onto the Mexican side of the border before the concrete had cured
Nice of most people discussing this to leave out that little detail.
As developers, we've all been there--would we react any differently?
"Your software is broken".
"I told you it was still in the alpha stage".
Really nothing to see here, move along...
|
|
|
|
|
dandy72 wrote: before the concrete had cured
FAKE NEWS!!!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Oh, you mean they removed the supports before the concrete was cured? That doesn't seem like it was a good idea.
|
|
|
|
|
|
Just looking at the couple of pictures I've seen.
|
|
|
|
|
I've only seen the one picture from the article (which starts the video, which I've not watched since this is such a non-story).
And I'm guessing that picture was taken as they were already in the process of tearing the whole thing down. So the forms could very well still have been in place when the whole thing tipped over.
|
|
|
|
|
OK, then it is like it didn't happen. There was an excuse; that handles it.
|
|
|
|
|
|
|
Hav YOU analyzed the chemical componund of that wall??
|
|
|
|
|
Please when you write parsers, separate your parsing logic from the rest of your app's logic so the app's main code isn't actually tied directly to your parser's grammar!
I mean, I get there's going to be some intermingling between different areas of your code
but when I crack open a project, and I find a codebase where every section of the app is intimately tied to every other section of the app it's really frustrating.
For example, the parser in this case returns LexSpan classes which hold a text buffer, and start and end positions within that buffer. Great for parsing, so you know where your fragments of text are.
But then when you build say, your Regex syntax tree with it, DO NOT use LexSpans as your member fields! unpack the values therein for witch's sake!
Now if i want to implement a different parser i have to completely tear apart the app's core logic.
Lovely.
Real programmers use butterflies
|
|
|
|
|
Take yourself to QA, and peruse a few dozen questions before you ask that.
Most of 'em can't spell "Emcapsull..." "Encapcalation" "Encrapsilating" "Encapsuoolasion" the word let alone use it!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: Most of 'em can't spell "Emcapsull..." "Encapcalation" "Encrapsilating" "Encapsuoolasion" the word let alone use it!
can be a bit tricky, so I do the other ting thng one.
after many otherwise intelligent sounding suggestions that achieved nothing the nice folks at Technet said the only solution was to low level format my hard disk then reinstall my signature. Sadly, this still didn't fix the issue!
|
|
|
|
|
I don't think I have ever seen lexer/parser code which wouldn't struggle to pass most code reviews.
|
|
|
|
|
Mine got a commendation ... 
|
|
|
|
|
Sounds like you need to send Uncle Bob around to visit them...
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
honey the codewitch wrote: LexSpan classes which hold a text buffer, and start and end positions within that buffer
So, a ReadOnlySpan<char>[^], but not as efficient? 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Well in this I will defend them, as ReadOnlySpan is only available on the latest non-DNF framework
Real programmers use butterflies
|
|
|
|
|
It's available in DNF 4.5 or later via a NuGet package:
NuGet Gallery | System.Memory 4.5.3[^]
The DNC version has slightly better performance, because some of the BCL methods have been updated to use it. But the DNF version should be at least as good as rolling your own.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
That's interesting. At one point i heard the DNF couldn't support stack alloc'd ref types the way DNC could but maybe I heard wrong.
Adding, the author intends to target .NET 2.0+ although i think that's a little silly.
Real programmers use butterflies
|
|
|
|
|
Some patterns don't become obvious until later on. If you're not into constant refactoring (due to fatigue or whatever), things stay.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
i don't think this code was all that factored to begin with. I think was just intended to be a quick and dirty port of lex basically, but then grew from there
Real programmers use butterflies
|
|
|
|
|
honey the codewitch wrote: Please when you write parsers,
That's all I needed to read.
You can take comfort in the fact that I've somehow managed to make it thus far in my programming career without ever having to write any sort of parser. Well, certainly not at the level you're dealing with.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
