On Sat, Dec 31, 2016 at 01:49:28PM +0100, Joh-Tob Schäg wrote:
> I think if Regenaxer adds a new function the function pointer and thereby
> the binary(assembly code) becomes invalid.
You misunderstood the question.
> > On Sat, Dec 31, 2016 at 12:28:06AM -0500, Bruno Franco wrote:
> > > I don't
I think if Regenaxer adds a new function the function pointer and thereby
the binary(assembly code) becomes invalid.
Am 31.12.2016 13:17 schrieb "Alexander Burger" :
> On Sat, Dec 31, 2016 at 12:28:06AM -0500, Bruno Franco wrote:
> > I don't really know any asm, but since
' is a read macro. (4 ' 4 7 8 6) is read is replaced a quoted version of
the next list/atom.
Not sure that helps try to understand the problem by drawing memory cells.
There is a structural difference which is handled in another ways by the
printer.
Am 31.12.2016 05:49 schrieb "Bruno Franco"
On Sat, Dec 31, 2016 at 09:11:37AM +0100, Joh-Tob Schäg wrote:
> As far as i know the picolisp assembler can change if now functions are
> added to the machine in abway to invalidates all asm. But not sure. If you
Uh? What changes? Can you be more clear?
--
UNSUBSCRIBE:
On Sat, Dec 31, 2016 at 12:28:06AM -0500, Bruno Franco wrote:
> I don't really know any asm, but since the asm code for the picolisp
> functions is just a (vi 'function) away, I feel tempted to try.
>
> I've found some advice on learning asm in general, but is there
> anything unique of the one
Hi Bruno,
> A picolisp clone of VI? That sounds awesome! Please do write the article
> for the wiki.
> Also, where do I find the source code?
Both scheduled for January :)
- Alex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe