For absolutely no reason I did the code for fash64 in Linux AMD64: type fash64 product as ulongint sum as ulongint declare sub begin() declare sub hash(x as ulongint) declare sub hashblock(xptr as ulongint ptr,n as ulongint) declare function finished() as ulongint end type sub fash64.begin() product...

The Fash Fast Hash Family. It should be easy to translate to FB I suppose:
https://github.com/douglascrockford/fash

The code is just infrastructure. It's not embedded in any environment for it to do anything interesting yet. So the associative memory will just remember a number of <input,target> patterns in arrays that you show it. The ENet version is somewhat similar but you have to give it all the examples at o...

This is the fastest evolving neural network I have so far:
https://drive.google.com/open?id=0BwsgMLjV0BnhdWltTF9BTGhfa3M

Linux AMD64 only.

What I like about Basic is case insensitivity clarity simplicity some built in graphic I'm very bored with Java, python doesn't compile to an exe (or not so easily), Nim I have to look more at, (Ruby) Crystal I will probably try with if I can get it to install. Anyway the current version of FB is ve...

If you wanted to make an effort designing a Basic then this site might help: http://hackingoff.com/ Realistically (unless you had a lot of time on your hands) it would have to be a minimal Basic. My thinking is to restrict primitive types to 64 bit signed int, 32 bit float,64 bit float,strings and p...

I have been using qrng.physik.hu-berlin.de for some years now.

Thank you. I signed up.

Dude!

The idea is to allow programming language mash-ups through simple file system message exchanges. Most programming languages allow interaction with the file system, I not sure access to unix sockets is always as available. However experts on such matters can correct me.

Cool, thanks for the further information. This is what I had come up with this morning minus what you have indicated. A middle-man which you start first: #include "crt/stdio.bi" const as string fifoA="/root/fifoA" shell("rm "+fifoA) shell("mkfifo "+fifoA) fope...

It does seem that a fifo is non-reusable. If true then you have temporal creation/open order issues to deal with, which are not fun. I guess you would need some piece of code sitting in the middle to delete an existing fifo, make a new one, then open the writer process, then open the reader process....

I've been experimenting with linux FIFO pipes and it's definitely a bit tricky and kinda non-robust. Anyway I've gotten this far: #include "file.bi" #include "crt/stdio.bi" const as string fifoname="/root/tempfifo" if not fileexists(fifoname) then shell("mkfifo &qu...

Then there is the array issue that never was properly handled in FB. I would say all arrays and user defined types should always be handled as pointers.

A storm in a teacup? Did someone drop some buttered bread on the floor? What happened? I don't know.