On Sun, Jul 16, 2017 at 9:24 AM, Alexander Burger wrote:
> On Sun, Jul 16, 2017 at 08:04:53AM -0400, Matt Wilbur wrote:
>> Reality just intervened - my MIPS processor is native 32-bit. So I think
>> emu is my only option. :(
>
> Well, it would also be possible to gener
On Sun, Jul 16, 2017 at 7:44 AM, Matt Wilbur wrote:
> On Sun, Jul 16, 2017 at 7:26 AM, Alexander Burger
> wrote:
>> On Sat, Jul 15, 2017 at 03:02:02PM -0400, Matt Wilbur wrote:
>>> Correct. I am working on a project that uses a MIPS processo embedded
>>> ...
>&
On Sun, Jul 16, 2017 at 7:26 AM, Alexander Burger wrote:
> On Sat, Jul 15, 2017 at 03:02:02PM -0400, Matt Wilbur wrote:
>> Correct. I am working on a project that uses a MIPS processo embedded
>> ...
>> I need the 64-bit PicoLisp, but MIPS isn't one of the
>> a
On Sat, Jul 15, 2017 at 7:21 AM, Jakob Eriksson wrote:
> Still, PicoLisp source, I mean the program you write in PicoLisp,
> (not the C code) can become quite large depending on your application.
>
> We mitigated this, not by storing the "compiled" structures of pointers
> to pointers. (Although w
On Sat, Jul 15, 2017 at 6:56 AM, Alexander Burger wrote:
>
> Hi Matt,
>
> > In order to minimize flash footprint, I was wondering if it would be
> > possible to compile code down to byte code? The reason i wanted to do that
> > is then I could make of some library functions in reader macros off-t
Hi everyone,
In order to minimize flash footprint, I was wondering if it would be
possible to compile code down to byte code? The reason i wanted to do that
is then I could make of some library functions in reader macros off-target
and avoid installing libraries on the target.
Matt
Please add me to the mailing list. picoLisp looks amazing.
