|
|
Take it to the Soapbox.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
You want a trade war in the soapbox?
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
Not enough coffee this morning? 
I think you wanted to post this in another forum
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.
|
|
|
|
|
|
I never considered Brexit a Political Argument, merely a concept of Common Sense vs Idiocy! (I argue for Common Sense! )
So, who decides or, adjudicates on this rule!
Is it Once more the case that as soon as English sensibilities are offended by the truth of Irish History, that laws, (in this case Posting Rules) are invoked to Silence the Irish?
I thought you to be a bigger Man Richard!
Bram van Kampen
modified 6-Aug-19 19:45pm.
|
|
|
|
|
I was merely pointing out that this is Soapbox material.
|
|
|
|
|
Point Accepted!
Bram van Kampen
|
|
|
|
|
|
|
I got a bunch of the console utilities done for my modular Parser Construction Kit
now you can do things like generate parsers and lexers, and i've almost got the bit where you can convert between different formats (so you can use Gold grammars with ANTLR or YACC, or my parser for example. or user ANTLR grammars with that same list, etc)
That's probably the coolest feature. Now people can use whatever grammars are available with whatever parsers are available.
That's still very experimental and my lexer conversion usually requires hand porting after-the-fact still.
I NEED TO SOLVE ARDEN'S THEOREM in C# to fix the above.
I'm vexed. Still, it's really amazing.
Now you can do like
@echo generating parser
ll1prep xbnf.pck | ll1gen /class XbnfParser > XbnfParser.cs
@echo generating tokenizer/lexer
ll1prep xbnf.pck | fagen /class XbnfTokenizer > XbnfTokenizer.cs
like a unix weenie
pretty soon:
xlate xbnf.pck xbnf.gold.grm
xlate xbnf.antlr.grm xbnf.yacc.y
etc
Now the question: the executable names are pretty general and i wanted to make them more specific to my project so you can put them in the path
the project suite is called pck so I was thinking
like either
pck.ll1gen
pckll1gen
pll1gen instead of just ll1gen
or
pck.xlate
pckxlate
pxlate instead of just xlate
what do you guys think for the naming?
i want it as short as can still be reasonable. Specific enough to avoid collisions on most systems (i don't need a guarantee)
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 think the names should be adjust to reflect your framework. Mostly because I have my own xlate utility but if those utilities are not very generic in their functionality they should be named more specifically in my opinion.
"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?"
|
|
|
|
|
i think so too, i'm just not sure which variation to use among the examples i listed, or perhaps a different one.
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.
|
|
|
|
|
Quote: I NEED TO SOLVE ARDEN'S THEOREM in C# to fix the above.
If you figure it out, let me know. I need to help a friend with it. Oh... Hang on a minute...
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
I hate that I can't solve it. All it does is turn a finite automata graph into a regular expression, basically
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.
|
|
|
|
|
From microsoft's response to visual studio user/customer requests:
Quote: We find that around 15% of the suggestions are challenging to act on, and they typically fall into the following buckets.
11% – Closed as duplicate
3% – Closed due to missing info from customer
1% – Closed because they were not suggestions for Visual Studio
My take from this: if requests are too hard might involve even a little real work:
1. wait until 2 people have asked the same question - close as duplicates.
2. something missed in the request? "shouldn't there be a comma there?" - closed.
3. did we ever say it would do that? yeah but exactly like that? No? - closed.
....
OK people, all those closed requests, please push them off the table straight into those [trash] buckets over there.
Wait! on second thoughts leave some behind in case other people ask for the same thing again.
so what's left? just this one?
someone requested a new icon? right! this we can do, let's go team, we've got work to do.
Message Signature
(Click to edit ->)
|
|
|
|
|
They didn't seem to mention the usual response:
We're too close to the next release to do this now. Closing as "wontfix".
Maybe that explains why they're releasing things much faster these days? 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I'm pretty sure that "1" in "15%" was meant to be a "9".
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!
|
|
|
|
|
No - the "5" was meant to be a "00".
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I'm just impressed that the numbers add up. 11+3+1 does indeed equal 15. They must have used Excel.  I mean really, this is a major milestone for any corporation, that the breakdown of their numbers adds up to the stated total. It's a miracle!
|
|
|
|
|
Marc Clifton wrote: They must not have used Excel.
Try entering the following two formulae in an Excel spreadsheet:
- =0.5-0.4-0.1 (displayed as 0, which is correct)
- =1*(0.5-0.4-0.1) (displayed as -2.77556E-17
 )
(The second result is actually accurate, is all values are doubles. Excel apparently attempts to "correct" for the fact that decimal fractions cannot, as a rule, be converted to an exact binary value.  )
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
That just proves they fudged the figures.
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!
|
|
|
|
|
Maybe a separate thing but what about "this behavior is by design"?
|
|
|
|
|
Does a Las Vegas doctor see you, and raise you one?
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!
|
|
|
|
|
Make sure you keep an eye on his hands.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
