Displaying 4 results from an estimated 4 matches for "interstice".
2004 Oct 21
2
[LLVMdev] Syn
...ng someone comfortable
with LLVM who would like to collaborate:
Executive summary: What if the syntax and semantics of a programming
language were specified in a library, rather than built into the
language, and thus could be swapped or extended at will just like any
other library?
http://www.interstice.com/journals/Simon/20041021.1.h.html
-Simon
2004 Oct 22
0
[LLVMdev] Syn
...who would like to collaborate:
>
> Executive summary: What if the syntax and semantics of a programming
> language were specified in a library, rather than built into the
> language, and thus could be swapped or extended at will just like any
> other library?
>
> http://www.interstice.com/journals/Simon/20041021.1.h.html
>
> -Simon
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev
2004 Aug 06
4
Re: Fwd: More fallback handling
...isy-chaining fallback sources. The primary souce would be used by various
broadcasters to send their programming, it's fallback would be a script
driven automatic playlist and it's fallback would be a jingle loop.
This way, there is programming if a broadcaster failed to connect and the
interstices between that "emergency programming" from scripts would be
filled by jingles.
In no case would clients get disconnected anymore.
The obvious pitfall and it's non-obvious solution is that, on stream
connect, I appear to steal the clients from it's fallback.
Because of the way...
2004 Oct 23
0
[LLVMdev] Re: Syn
>How is this different from the LISP and scheme macro system? The
>program source is available to the programmer at both compile and
>run-time and may be operated on arbitrarily (transforming code, adding
>code, removing code, specializing code, making new "primitives",
>modifying other macros, etc). There is a reason for LISP's syntax, it
>is so you can program