CallStream + project Euler

I am currently in the stage of searching for simple but valid examples of CallStream validity (aka: usefulness) as interfacing concept and programming idiom.

Leonhard Euler
Leonhard Euler

And, I think I have found one. CallStream + project Euler. The mathematical nature of some computational problems make them a great fit for the functional paradigm. For those of you who don’t know, “Project Euler is a series of challenging mathematical/computer programming problems…” ( I have concluded I could use the simple and interesting solution for a problem from “Project Euler” to show CallStream in action.
Continue reading “CallStream + project Euler”

CallStream Part 3 : C++ Binding

A paradigm shift (or revolutionary science) is, according to Thomas Kuhn, in his influential book The Structure of Scientific Revolutions (1962), a change in the basic assumptions, or paradigms, within the ruling theory of science. It is in contrast to his idea of normal science.

CallStream Part 3 : C++ Binding

Good old C++ is one strongly typed language. CallStream concept is born (and bred) in the domain of type-less JavaScript. Also, C++ is (so called) static (compiled) language, vs dynamic (interpreted) JavaScript. C# is somewhere in between, (but not in the middle !) especially in it’s latest 4.0 reincarnation. Still I think CallStream should be implemented in C++ too. Why?
Continue reading “CallStream Part 3 : C++ Binding”

CallStream. Interfacing and application architecture pattern


I am one of those people who think that JavaScript should not be changed. No new keywords should be added. If anything, some should be removed, like ‘new’ for example. But there is one concept and one keyword which is missing: interface

Originally published 2010 Mar 05
Continue reading “CallStream. Interfacing and application architecture pattern”