Re: Push in prop lists

2015-08-25 Thread Alexander Burger
Hi Oscar, > Hi, I've been trying to figure out how to properly push into a > property list but the behavior seems kinda strange. > > IE: > :eee is a test class instance and vwp is a number list (2 1 4) > (push (get :eee 'vwp) 10) -> ((10 . 2) 1 4) You cannot use 'get' here, because it returns th

Re: low level VM and disassemble

2015-08-25 Thread Alexander Burger
Hi Erik, > I imagine something like CL's 'disassemble' that, given an arbitrary lisp > expression, returns the sequence of VM instructions the expression maps to. To extend a little what Tomas and Andreas said: I think it is not so very useful to look at the generated native ASM code, as it more

Push in prop lists

2015-08-25 Thread Oscar
Hi, I've been trying to figure out how to properly push into a property list but the behavior seems kinda strange. IE: :eee is a test class instance and vwp is a number list (2 1 4) (push (get :eee 'vwp) 10) -> ((10 . 2) 1 4) And when calling prop returns -> (((10 .2) 1 4) . vwp) Which is useless

RE: low level VM and disassemble

2015-08-25 Thread andreas
Hi Erik First, the fundamentals are documented in the picolisp dir @doc64/ Look there for a start, if you haven already. Do you have Vi or Vim installed? If so, there is a great lookup function which does what you described. Start pil repl with debug mode: $ pil + Use the vi function to look up

Re: low level VM and disassemble

2015-08-25 Thread Tomas Hlavaty
Hi Erik, one of the immediate steps for pil64 compilation goes through asm file. You can study that. Otherwise picolisp doesn't have a disassembler and it also doesn't have a compiler. Cheers, Tomas Erik Gustafson writes: > Hi List, > > I'd like to develop a better intuition for how things w

low level VM and disassemble

2015-08-25 Thread Erik Gustafson
Hi List, I'd like to develop a better intuition for how things work in the lower levels of 64bit PicoLisp, how cells are passed between registers, and all that. I need to spend more time with the code in /src64 and going over the docs, obviously. Any other ways you all have found to be effective i

Re: ins@nity

2015-08-25 Thread Erik Gustafson
> I starred it on github - the README deserves it purely on its own > merits :-D ...and the link to Infected Mushroom of course. I'm > guessing there too much coffee was involved? > Hey, thanks! It was getting late and the filter between my thoughts and what gets pushed to github was malfunctionin

RE: ins@nity

2015-08-25 Thread andreas
- Original Message - From: andreas.rueeg...@itship.ch [mailto:andreas.rueeg...@itship.ch] To: picolisp@software-lab.de Sent: Tue, 25 Aug 2015 14:32:24 +0200 Subject: I like it! I will not use it in my work, but I find it a nice piece of coding art. It might help some people to understand

Re: ins@nity

2015-08-25 Thread Rowan Thorpe
On 25 August 2015 at 07:32, Erik Gustafson wrote: > ..[snip].. > https://github.com/erdg/insanity I starred it on github - the README deserves it purely on its own merits :-D ...and the link to Infected Mushroom of course. I'm guessing there too much coffee was involved? -- PGP fingerprint: BB

Re: ins@nity

2015-08-25 Thread Erik Gustafson
Great question. Apologies if that was lost amongst the rest of the nonsense there. It simply provides an alternate syntax for the mapping functions (mapcar, seek, fish, etc). Instead of, (mapcar '((X) (doThings X) (1 2 3) ) you can write, (mapcar@ (1 2 3) (doThings @) ) Same idea appl

Re: ins@nity

2015-08-25 Thread jakob
Haha, I looked at it but what is it? :-) On August 25, 2015 6:32:28 AM CEST, Erik Gustafson wrote: >What's good everyone? > >I've really been liking the function 'map@' from a few threads back. I >wrote a little library that follows this idea to its logical >conclusion. >It's mostly a joke, so