|
Any price is too high for a merkin.
|
|
|
|
|
|
It seems that BBC blocked (no bbc.com and no bbc.co.uk) in my company firewall - the only site I can remember years back that I can't load...
But thinking of it - it is probably the best advert 
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
|
I was tired of xmas way back in June when the first xmas-oriented tv commercials started appearing...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
#realJSOP wrote: I was tired of xmas way back in June when the first xmas-oriented tv commercials started appearing
That's more like it.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
|
I suggest playing Cthulu Carols instead. Way more enjoyable to listen to. 
Cthulhu carols - YouTube
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
On Sunday I almost went to the local mall to buy some panadol,
just in time remembered the time of the year.
taking a nap instead: worked a treat.
this internet has become nothing but fake news.
... time to fix it, time to get back to the fax!
|
|
|
|
|
I was tired of this year's ads at least a year ago.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
So I'm about to post the parsing portion of Slang as a code project article. I've decided to do them in a series.
The trouble with the parser is it requires a binaries i built (two to be precise) to be included because it references them in a build step.
Now, my options are:
1. Include the binaries with the source redistributable (i like this idea because it doesn't distract from the parser project while still allowing editing of the master lex file - the code it generates will be generated from that document
2. Forgo the pre build step and just make that portion of the project static, but the tool isn't necessary.
3. Include the source for those tools as part of the solution - i don't like this as they're rather large, and I already produced articles for them. I feel like they would distract.
What's your take?
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.
|
|
|
|
|
honey the codewitch wrote:
The trouble with the parser is it requires a binaries i built (two to be precise) to be included because it references them in a build step.
... and I already produced articles for them. I feel like they would distract.
can you not just add links to those earlier articles?
- assuming they would have the source (github?) [for those that don't trust binaries]
this internet has become nothing but fake news.
... time to fix it, time to get back to the fax!
|
|
|
|
|
I would, but without them part of the project cannot rebuild. That's okay, it's one of the options i alluded to, but it just means the full gamut of modifications cannot be done (it's near impossible to modify the lexer tables by hand - you need the tool to produce those arrays)
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.
|
|
|
|
|
Put the binaries up on NuGet and reference that?
That way, each article can be "used in isolation" but without the large size (the size becomes MS's problem not CPs).
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Guess I get to learn how to make a nuget package then, but can they actually set up some binaries in the *source* (not bin) directory without adding them as a reference to any projects? that's what I'd need.
Sorry i know very little about them, except including them in my projects. Thus far i haven't had a need to build them until now maybe.
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.
|
|
|
|
|
Absolutely no idea! 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I think I'll skip that route for now. I may go with #2 though. It seems people in general aren't keen on including the binaries. I'll add a section on setting up the pre build step in the article, and reference the article for Rolex, the tool i use to generate the tokenizer.
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.
|
|
|
|
|
Binaries are a problem - you never know what you are going to get, even with a CP download.
No idea why, but I "Trust" NuGet binaries more than CP. strange, but true.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Since you already made articles for those binaries it's enough to link to the articles and include the binaries with the source.
Otherwise I would have said you should include source for them as well.
|
|
|
|
|
You're the only one that came down on including the binaries with the source so I've decided to go with option #2 and provide instructions on setting up the build step and putting the binaries where they need to be.
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.
|
|
|
|
|
Well you got three different answers. 
Do what's easiest, as long as one can recreate a working project.
|
|
|
|
|
I did, and thanks for your input. Usually I find asking helps, even if it just helps lead me my own way. I get "stuck" in analysis paralysis, and asking can often "unstick" me.
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.
|
|
|
|
|
honey the codewitch wrote: analysis paralysis
My nemesis.
|
|
|
|
|
As others have said you could make the binaries available on NuGet, but I would also include in the article a link to your previous articles that tell how to make those binaries.
Just because the code works, it doesn't mean that it is good code.
|
|
|
|
|
I don't know that NuGet will let me do what I need to do since these projects are not referenced binaries, but rather binaries included in the *source directory* used during a pre-build step, and not during execution.
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
So the missus got what she wanted...a live tree this year.
Bah! Humbug! I can't wait until it's over!