George Orais <gpor...@yahoo.com> writes:

Hi George,

> The pilMCU is the PicoLisp interpreter itself :) To interact with it,
> as of the moment we will use UART and use a PC as terminal. But later
> we plan to add PS/2 and VGA as the means to inter act with the
> hardware interpreter, i hope this answer your inquiry? Thanks!

Yes, thank you!
This stuff is exciting, but a bit new for me too ...

> On Monday, September 22, 2014 5:29 PM, Thorsten Jolitz
> <tjol...@gmail.com> wrote:
>
> Alexander Burger <a...@software-lab.de> writes:
>
> Hi Alex,
>
>>> Assuming PilMCU hardware exists and someone wants to use or program
>>> it, how
>>> would that look like? Where would one type the commands to manage
> the
>>> file system (whats the PilCMU terminal/console?), how would one
> interact
>>> with the PicoLisp REPL?
>>
>> You saw the copy/pasted session in my first post? That's exactly how
> you
>> interact with it.
>
> yes, but I wondered what would be the device the PicoLisp REPL runs on
> in this case. 
>
>> We have two I/O ports defined as TTY in- and output. On the real
>> hardware you connect a terminal(program).
>
> ok
>
>> The SSD images contain a database, with a simple file system
> implemented
>> in external symbols. These images are generated with a normal
> PicoLisp
>> running on a standard PC, and then transferred t o the SSDs.
>
> ok
>
>> I made the images so far by copying normal *.l files from standard
>> PicoLisp to an "init/" directory, and edited the files so that they
> were
>> the way we need them for PilMCU.
>
> thanks for the info!

-- 
cheers,
Thorsten

-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Reply via email to