gmane.lisp.picolisp.general

Re: REPL and OpenGL

Oskar Wieland — 2013-06-10T13:42:00

Hi alex,

setting a background task was exactly what I was looking for.

(task -10 0 (...)) works fine.

I tried it with the socket fd also, by reading it from /proc/<PID>/fd/ 
and putting it into

(task <socketFd> (glutMainLoopEvent))

but got only segmentation faults.

Thanks a lot
Oskar

Re: REPL and OpenGL

Alexander Burger — 2013-06-07T15:42:01

If such a file descriptor is indeed not available, then simply replace

   (catch 'quit (glutMainLoop))

with

   (task -10 0
      (native `*GlutLib "glutMainLoopEvent") )

i.e. set a background task with a 10 msec timeout.

♪♫ Alex

Re: REPL and OpenGL

Alexander Burger — 2013-06-07T13:01:43

Hi Oskar,


Yes ... as I said in my last mail:

   Can we find out the socket fd where the events arrive on?

   If so, then I would trigger 'glutMainLoopEvent' whenever an event
   arrives:

   (task <socketFd> (glutMainLoopEvent))

So you must put the call to (glutMainLoopEvent) into a background task.
The same mechanism is used in the PicoLisp GUI, for example.

Then you have the normal ':' prompt and you can debug your program while
the OpenGL output runs in the separate X11 window.

But 'task' either requires a file descriptor (a positive number,
typically a socket) or a timeout value in milliseconds (a negative
number). The timeout is probably not so useful, so the question is if it
is possible to get hold of some file descriptor (socker, pipe or
whatever) where the X11 events are signalled.

♪♫ Alex

Re: REPL and OpenGL

Oskar Wieland — 2013-06-07T06:40:04

Hi,

thanks for the suggestions but I couldn't find a way to get it worrking 
together.

Maybe I didn't made myself clear enough, the link shows what I'm trying 
to do:

Lisp, Opengl and live editting of code:
http://www.youtube.com/watch?v=XLkUI89fgRI

Is this possible with picoLisp?

Regards
Oskar

Re: Syntax for global variable in namespace?

Thorsten Jolitz — 2013-06-02T12:00:09

Hi Alex,




OK, thanks for the info.

Re: Syntax for global variable in namespace?

Alexander Burger — 2013-06-02T11:09:10

Hi Thorsten,


I would say that '*Var' is all right.



Yes. Also, 'Var' is meant to denote symbols which are bound
locally/dynamically.



Yes. I haven't seen or used many constants yet (a good case might be
"lib/openGl.l" though), but an all-uppercase notations seems natural to
me.

One thing to remember is of course that there are no real "constants" in
PicoLisp. Anything may be modified at any time.

♪♫ Alex

Syntax for global variable in namespace?

Thorsten Jolitz — 2013-06-02T09:49:23

 
Hi List,   when I write a library with its own namespace, and want 
a 'global variable' in that namespace that stores 'vital 
information' for the library - do I use the '*Var' syntax or is 
that reserved for variables that are really global in PicoLisp?

I could of course just name it 'Var', but the '*Var' would 
underline its importance.    BTW 
Are constants in uppercase (like 'MYCONST') acceptable in PicoLisp?

Re: Assign a list as symbols property list

Thorsten Jolitz — 2013-06-02T09:30:55

Hi Alex,


I see, fortunately my "real" list has the right order ...


I knew that there must be a function for this ... thanks

Re: Missing "o" in "-lcrypt" in scr/Makefile

Alexander Burger — 2013-06-02T07:09:46

Hi Jon,

OK, so for now I moved "-lcrypt" flag to a Makefile variable LCRYPT, and
assigned "-lcrypto" for Darwin and the BSD family.

Though it doesn't give strong encryption at the moment, at least it
compiles and is better than nothing ;-)

♪♫ Alex

Re: Assign a list as symbols property list

Alexander Burger — 2013-06-02T07:02:38

Hi Thorsten,


Note that the list has the cons pair elements reversed:

   ((value1 . key1) (value2 . key2) ... (valuen . keyn))




This can be done with 'putl'.

♪♫ Alex

Assign a list as symbols property list

Thorsten Jolitz — 2013-06-01T19:06:12

Hi List, 

probably a rather newbie question:

When I already have property list like 

,------------------------------------------------------
| ((key1 . value1) (key2 . value2) ... (keyn . valuen))
`------------------------------------------------------
 
and want to assign the whole thing as a symbols property list - how do I
do that (without setting every single key/value pair with 'put')?

Re: Missing "o" in "-lcrypt" in scr/Makefile

Jon Kleiser — 2013-06-01T16:13:29

Hi Alex,


I'm not shure what kind of crypt() functions that's available on the Mac,
but if I use 'irb' (i.e. Ruby 1.8.7) with OSX 10.8.3, then I get this:

=> "$6bsuufIMFxJE"

.. the same (worthless) DES algorithm. I'll try to find out more about
this, a little later.

/Jon

Ersatz Proposal: Interface implementations should return standard

Samuel Dennis Borlongan — 2013-05-30T15:32:43

Currently, if the resulting object from an 'interface' invocation is
supposed to implement a method that returns values (like Supplier in Java
8):

(setq String (interface "java.util.function.Supplier" "get" '(() (java
"java.lang.String" T "java.lang.String") ) ) )

Then, if the implemented method is invoked on the object:

(java String "get")

The returned value is of the type PicoLisp$Symbol, since the curent
implementation of interface returns the PicoLisp$Any result from evaluating
the PicoLisp function bound to that method.

Unfortunately, this means that there would be no way to retrieve the values
returned from that interface implementation's method unless you implement
heavy field-based recursion on the Any object.

Fortunately, I've made a modification to interface that allows PicoLisp
users to not only return Java values from interface implementation methods,
but also all 5 possible value types from PicoLisp (T, NIL, Number, Symbol,
and Cell):

What I've done is to replace the "return a;" statement

Re: Missing "o" in "-lcrypt" in scr/Makefile

Alexander Burger — 2013-05-30T15:12:41

Hi Jon,


Hmm, yes and no ...

It works, but obviously only with the (worthless) DES algorithm, because
the generated hash is much too short.

In glibc's crypt() more modern algorithms are supported:

   The glibc2 version of  this  function  supports  additional  encryption
   algorithms.

   If  salt is a character string starting with the characters "$id$" fol‐
   lowed by a string terminated by "$":

          $id$salt$encrypted

   then instead of using the DES machine,  id  identifies  the  encryption
   method  used  and  this  then  determines  how the rest of the password
   string is interpreted.  The following values of id are supported:

          ID  | Method
          ─────────────────────────────────────────────────────────
          1   | MD5
          2a  | Blowfish (not in mainline glibc; added in some
              | Linux distributions)
          5   | SHA-256 (since glibc 2

Re: Missing "o" in "-lcrypt" in scr/Makefile

Jon Kleiser — 2013-05-30T14:45:31

Hi Alex,


I did this:

$ ./pil lib/adm.l +
: (de *Salt 16 . "$6$< at >1$")
-> *Salt
: (passwd "somestring")
-> "$6bsuufIMFxJE"

So it seems that the 'passwd' function is working in 32-bit PicoLisp on
Mac, right?

/Jon

Re: Problems with 'call'

Thorsten Jolitz — 2013-05-29T17:41:02

Jorge Acereda Maciá <jacereda-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>
writes:


I didn't - that solved the problem, thanks!

Re: Problems with 'call'

Jorge Acereda Maciá — 2013-05-29T17:18:12

On May 29, 2013, at 7:05 PM, Thorsten Jolitz <tjolitz-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

Did you export it? (export FOO=x instead of just FOO=x)

Re: Problems with 'call'

Thorsten Jolitz — 2013-05-29T17:05:27

Hi Alex,


I still get the same error. 

,----------------------------------------------------------
| $ $WEKAHOME
| -bash: /home/tj/java/weka/weka-3-6-9: Ist ein Verzeichnis
| $ $TERM
| -bash: xterm-256color: Kommando nicht gefunden.
`----------------------------------------------------------

the variable is set and known to BASH, but somehow PicoLisp does not
know about it:
,--------------------
| : (sys "WEKAHOME")
| -> NIL
| : (sys "TERM")    
| -> "xterm-256color"
`--------------------

Re: Problems with 'call'

Alexander Burger — 2013-05-29T16:34:51

Hi Thorsten,


The shell expands the variable $WEKAHOME when it evaluates the command
line, which does not happen if you call "java" directly.

You might try this:

   (call "java"
      "-cp"
      (pack (sys "WEKAHOME") "/weka.jar")
      "weka.classifiers.functions.SMO"
      "-h" )

♪♫ Alex

Problems with 'call'

Thorsten Jolitz — 2013-05-29T16:02:48

Hi List,

why does this work in the Shell command line:

,----------------------------------------------------------------
| $ java -cp $WEKAHOME/weka.jar weka.classifiers.functions.SMO -h
|
| Help requested.
|
| General options:
|
| -h or -help
|         Output help information. [...]
`----------------------------------------------------------------

but this does not work in the PicoLisp commandline:

 ,---------------------------------------------------------------------------------
 | : (call "java" "-cp" "$WEKAHOME/weka.jar" "weka.classifiers.functions.SMO" "-h")
 | Fehler: Hauptklasse weka.classifiers.functions.SMO konnte nicht
 | gefunden oder geladen werden
 | -> NIL
 `---------------------------------------------------------------------------------
[TRANSLATION: Error: class weka.classifiers.functions.SMO could not be
found or loaded]

--
cheers,
Thorsten

Re: REPL and OpenGL

Jorge Acereda Maciá — 2013-05-28T18:07:26

A couple of options:

- Use coroutines and yield control to the main thread in the glutIdleFunc.
- Use a library that doesn't take control of the main loop. I can think of mine ( http://code.google.com/p/libaw/ ) and GLFW ( http://www.glfw.org ).


On May 28, 2013, at 10:57 AM, Oskar Wieland <oskar.wieland-Mmb7MZpHnFY< at >public.gmane.org> wrote: