|
Nice.
I've seen them live, about 15 years ago or so...
15 years... And now I'm depressed
|
|
|
|
|
|
Catchy!
|
|
|
|
|
One minute into this video I also found a nice sound: Rugbeater[^]
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.
|
|
|
|
|
|
Very, very, nice … Actually is it also quite heavy, as for my ears ...
In the DM/DC area, I was impressed recently by the latest
albums of "Shadow of Intent" and "TAIM",
Cheers,
|
|
|
|
|
|
yep … I will be looking for the albums tomorrow to buy them …
Have a nice weekend,
Cheers,
|
|
|
|
|
Here is some beautiful piano music you might like: "The Lake". The other Herman Beeftink songs in that list are also very good.
|
|
|
|
|
|
Have fun with your skill improvement!
|
|
|
|
|
they really need to unify these different .NET platforms (Core vs Windows)
right now, because of the ugliness of using core console apps from a windows command line, i've made a windows executable, and packaged all my commands up into one monolithic exe. I'll make a similar core exe too, using the same codebase (stupid, i know)
The reason for the monolithic exe was that it was the difference between creating 2 projects or 10 projects.
Anyway, i don't like having to workaround all this crap. I'd have probably broken my app up differently in .NET 5. As it is here's my usage screen
Usage: pckw <command> [<arguments>]
Commands:
pckw fagen [<specfile> [<outputfile>]] [/class <classname>] [/namespace <namespace>] [/language <language>]
<specfile> The pck specification file to use (or stdin)
<outputfile> The file to write (or stdout)
<classname> The name of the class to generate (or taken from the filename or from the start symbol of the grammar)
<namespace> The namespace to generate the code under (or none)
<language> The .NET language to generate the code for (or draw from filename or C#)
Generates an FA tokenizer/lexer in the specified .NET language.
pckw ll1gen [<specfile> [<outputfile>]] [/class <classname>] [/namespace <namespace>] [/language <language>]
<specfile> The pck specification file to use (or stdin)
<outputfile> The file to write (or stdout)
<classname> The name of the class to generate (or taken from the filename or from the start symbol of the grammar)
<namespace> The namespace to generate the code under (or none)
<language> The .NET language to generate the code for (or draw from filename or C#)
Generates an LL(1) parser in the specified .NET language.
pckw ll1 [<specfile> [<outputfile>]]
<specfile> The pck specification file to use (or stdin)
<outputfile> The file to write (or stdout)
Factors a pck grammar spec so that it can be used with an LL(1) parser.
pckw xlt [<inputfile> [<outputfile>]] [/transform <transform>] [/assembly <assembly>]
<inputfile> The input file to use (or stdin)
<outputfile> The file to write (or stdout)
<transform> The name of the transform to use (or taken from the input and/or output filenames)
<assembly> The assembly to reference
Translates an input format to an output format.
Available transforms include:
pckToLex Translates a pck spec to a lex/flex spec
pckToYacc Translates a pck spec to a yacc spec
xbnfToPck Translates an xbnf grammar to a pck spec.
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.
|
|
|
|
|
.Net WAS unified, and then they muddieid the water with .Net Standard and .Net Core, which are both apparently different from .Net Framework.
.Net Core is a fix looking for a problem.
|
|
|
|
|
basically i agree since I already can run .NET PEs on linux.
still, i build in .NET core because i'm not sure how deep that compatibility runs - for example, will only linux run a .NET win PE, or will anything running mono be able to? what about the other CLR/CLI implementations, etc? these are all questions I don't currently know the answer to and there are plenty more too. And I don't want to have to find out the answers. So I build in core
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.
|
|
|
|
|
As long as you don't have a UI, your ,net *framework* app should run on linux/mono. Keep in mind that mono (last time I checked) was SEVERELY behind the power curve as far as .net versions are concerned. If your app DOES have a UI, you may be able tio run it under Wine, but I see that as at least as much of a crap shoot as using mono.
As an alternative, you might want to try writing your code in C++.Net, get it working there, and then ciopying the source code (the cpp files) to a Linux C++ project, and try compiling it native on linux.
I've generally found that as we progress in dev technology, we get further away from being able to do cross-platform dev. This has been a problem ever since Windows was first introduced.
|
|
|
|
|
I'm not going to do this in C++ as there are already a zillion parser generators out there in C++
This one lets you use those tools with it at least. (Yacc/Bison and Lex/Flex supported so far)
I'm fine working with Core and the Desktop app for now.
The only gui app I have isn't necessary to use the tools. It's just a bonus more or less.
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.
|
|
|
|
|
|
Actually I've been considering targeting both javascript and SQL92 with my parsers and tokenizers.
Yes, parsing in SQL
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.
|
|
|
|
|
Here we go angry mobbing again...
Since you've been more active here I always have my torch and pitchfork close
|
|
|
|
|
If I target SQL I deserve it.
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.
|
|
|
|
|
The fix for this (for the moment) is to code against .NET Standard. That will cover both core and framework use cases.
It's not ideal, but it works.
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
|
|
|
|
|
.NET Standard 2.0 doesn't support console apps AFAIK
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.
|
|
|
|
|
No, code against .Net Framework - I'm sure the other versions will just fade away if we all ignore them long enough.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
heh.
I've got two executables with the same codebase. They're just compiled with different settings - one is Core and the other is DNF
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.
|
|
|
|
|
You are just not ignoring .Core hard enough!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|