Viewing profile — mckinney

This is already implemented with manifold's unit expressions, but is made richer and more readable via concatenative features. For instance, '1.5 * USD' is not as readable as simpl…

Ha! I implemented "concatenative" programming for Java as Binding [1] (or Unit) expressions, but had no idea. Seriously, never came across that term before this post. The idea with…

So, choke the oceans too? Which is it? Is corn-derived ethanol a fabulous "renewable energy", or is it yesterday's bad idea?

Except, if not for environmentalism, this mess would not exist.

California policy makers' (ardent environmentalists) "Low Carbon Fuel Standard" require 10% corn-derived ethanol in gasoline sold in the state. Are they not environmentalisting har…

And end government subsidized corn vis-à-vis ethanol production.

I suggest you do a bit of reading if you truly don't understand that corn ethanol is widely considered a "renewable fuel."

https://en.wikipedia.org/wiki/Corn_ethanol

Another ridiculously ironic consequence of environmentalism. But do keep the "renewable" energy train running at all costs.

Thank you! Yes, Manifold already supports Java 15 multi-line strings (aka text blocks) like this: var myValue = """ [>.js You can embed a resource fragment as either a declaration …

Right, but that is just syntax highlighting. This is resolving the content of the string type-safely, at compile-time.

> but is there really a need to have this kind of language interoperability at compile time? Well, if you want to leverage Java's static type system (and why not?), the answer is, …

> Good IDE lets you move between the resource file and the code with a single click. Well, not exactly. Most IDEs do NOT support clicking through a generated method call to the cor…

At compile-time manifold-js[1] parses JS and generates Java types (stubs), which forward execution to rhino at runtime. Basically, JS seamlessly mapped onto Java's type system. [1]…

Hi, you can blame me for this. It's a Java compiler plugin[1], which is similar to an annotation processor, but can hook into the compiler at a much earlier stage, which allows it …

In most cases, the devs that should be concerned about debugging generated code are the authors of the generator. If there are bugs in released code, consumers of the API should fi…

You can see the generated code in the IDE via Edit | View Java Source when a resource is selected. And you can debug it as well. Sort of the best of both worlds. What makes Manifol…

But the main idea with this is to avoid the pitfalls of conventional code generation such as GQL Code Generator. See "The Big Picture"[1] in the core docs. [1] https://github.com/m…