Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - ssqq

Pages 1 2 3 4 5 6
#31
Anything else we might add? / How to make destructive function
July 15, 2016, 02:09:09 AM
some newLISP builtin function is destructive, If user want design destructive function, how to make it?



for every argument passed into user function is value, not reference only if value is stored in a functor.
#32
Anything else we might add? / not nil? and not true? value
July 09, 2016, 10:35:37 PM
I found '() is not nil or true? value:


Code Select

> (nil? '())
nil
> (true? '())
nil
> (empty? '())
true
> (list? '())
true
> (= '() '())
true


for nil and true is only bool value in newLISP, so everything should be judged with nil? or true?
#33
Anything else we might add? / Re: functor name error [a..e]
July 08, 2016, 06:12:35 AM
thanks, I get it use 10.6.0, I would try it use 10.7.0.



when I use 10.7.0 it is ok.
#34
Anything else we might add? / Re: Strange reader
July 05, 2016, 09:35:04 PM
I think this is a bug.



symbol table should permit "fn" or "lambda" as name.
#35
Anything else we might add? / functor name error [a..e]
July 05, 2016, 09:31:17 PM
Code Select

> (define a:a)
ERR: context expected in function define : a
> (define b:b)
ERR: context expected in function define : b
> (define c:c)
ERR: context expected in function define : c
> (define d:d)
ERR: context expected in function define : d
> (define e:e)
ERR: context expected in function define : e
> (define f:f)
nil
#36
newLISP newS / Re: newLISP Development release 10.4.6
July 26, 2015, 01:12:55 PM
YAML is suit for view, C and C++ YAML LIB have been upgrade to 1.1.



http://pyyaml.org/wiki/LibYAML">//http://pyyaml.org/wiki/LibYAML



Anyone could test it in newlisp.
#37
Anything else we might add? / Re: Ceramic: bring web apps to desktop
July 26, 2015, 01:06:53 PM
Website is so quickly, If give some compare data with other website framework. I think maybe Google would interest with it.
#38
Whither newLISP? / Why first lambda expression is args
July 06, 2015, 01:52:25 AM
I think first lambda expression should is 'lambda:


Code Select

> (first (lambda (x y) (+ x y)))
lambda
> (first (fn (x y) (+ x y)))
fn
> 'lambda
lambda
> 'fn
fn
> (cons 'fn '((x y) (+ x y)))
(fn (x y) (+ x y))


Why newLISP use args as first elements of lambda expression?

Why could not quote *lambda* and *fn*?
#39
Anything else we might add? / add function defined?
July 06, 2015, 01:44:33 AM
I think newlisp  should add function *defined?*, for all not defined variable is *nil*.


Code Select


> (defined? 'var) ; --> nil
> (set 'var nil)
> (defined? 'var) ; --> true
> (delete 'var)
> (defined? 'var) ; --> nil
#40
Anything else we might add? / Some Advise about newLISP
May 14, 2015, 05:19:43 AM
I like newLISP.



If put the source code to github. maybe more people could participate in this Project.



If Add some function used 'Test` in newLISP core like this:


       
Code Select
( is (expression args) result, messsage))
                 ( ok expression-is-true message)

Then could add some test-case in core. So many people could see sample in source code.



Add Core-Module-List in newLIsp.com, with registered download address, then We could write code to download module, install it then test it automatically.
#41
So, what can you actually DO with newLISP? / un-declare symbols check tool for newLISP
January 13, 2015, 04:24:37 AM
I write a tool for checking un-declare symbol of newLISP code, it need improve more.



https://github.com/songzan/Spp/blob/master/strict.lsp">https://github.com/songzan/Spp/blob/master/strict.lsp



If you want test it, pls link it first (or change default *main-args* number):



On Winxp:



       > newlisp -x strict.lsp strict.exe

       > strict your-script.lsp



On Linux:



      > newlisp -x strict.lsp strict

      > chmod 755 strict

      > ./strict your-script.lsp



1. all un-declare symbol would output an warning.

2. all un-used symbol declared with *local*, *let*, *letn*, *letex* would output an warning.

3. all symbol declared with *set* or *setq* in *lexical scope* would throw an warning.



todo:



1. could not check the symbols *import* from C module

2. could not check *other* context symbols.

3. could not check symbol created with *new* or *bind*.

4. warning message have not the line number and pos message.



welcome give me some suggest.
#42
newLISP in the real world / Ubuntu 14.04 newLISP repl, up,down,right,left key is valid
January 13, 2015, 04:04:55 AM
When I use the key of *up* *down* *right* *left* in REPL with Ubuntu 14.04 shell:


Code Select


ssqq@X61:~$ newlisp
newLISP v.10.6.0 32-bit on Linux IPv4/6 UTF-8, options: newlisp -h

> ^[[D^[[C^[[B^[[A^[[A^[[C



I try other shell or ssh tool, same problem. If I missed some compiler file when built newLISP?
#43
newLISP in the real world / eval context symbol error
January 09, 2015, 04:28:53 AM
I found if *eval* a symbol, then *eval* the context symbol with this symbol prefix would throw a error.


Code Select

> (eval 'c)
nil
> (eval 'c:var)
ERR: context expected in function eval : c
> (context 'c)
c
> (eval 'c:var)
nil
#44
Anything else we might add? / Re: C-style atexit functions?
January 07, 2015, 07:46:32 PM
yes, When we import some module, imported symbols list is useful, when it is not useable, delete it from symbols table also is a good habbit.
#45
So, what can you actually DO with newLISP? / newLISP syntax check tool
January 07, 2015, 06:32:43 PM
Hi, I write a newLISP syntax check tool with perl6.



https://github.com/songzan/Spp/blob/master/Newlisp.p6">//https://github.com/songzan/Spp/blob/master/Newlisp.p6



Could pass with all lsp file with contribute package.



found following error:



module/unix.lsp line: 59
Code Select
   (import library "getuid")`
end char is *`*.
Pages 1 2 3 4 5 6