The emulation/translation in my product is: There is underlying strongly typed native code that is bound to dynamically typed scripting languages (Javascript and Lua). On the visual programming side, each node can bind to native or script data types via ports. Those ports...
-
-
Prikaži ovu nit
-
normally are strongly typed, and the UI prevents sending things like image data buffers to incompatible input ports. But, sometimes, I need to treat the image buffer as an array or list to be read in to the next node, rather than as a native type. And the script VM accepts...
Prikaži ovu nit -
all data as opaque types (as it should), so, there was a need to create a QD_ANY type, with type "hints" as to the structure of that input data, and it's left to the end user to correctly unpack the data correctly according to its pointer ISA type. It's a trade off, as...
Prikaži ovu nit -
using this approach can introduce side-effects and dynamic runtime errors that weren't possible in the pure strongly typed version, but the product gains the feature of defining new types at design time & runtime, which is powerful and allows the end user complete control vs. ...
Prikaži ovu nit -
having to find environment specific kludges or much larger flows to represent simple structures (as abstractions), like many have to do in vanilla Pure Data when the end user lacks the ability to program a lower level external (natively coded nodes)
Prikaži ovu nit
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.