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 - limux

Pages1
#1
newLISP in the real world / Re: Bug of (context Foo)?
November 02, 2013, 07:18:21 AM
Very thanks and Best Regards.
#2
newLISP in the real world / Re: Bug of (context Foo)?
November 02, 2013, 06:00:04 AM
even (symbol? Foo) will implicit introduce a symbol. That is newLisp style!
#3
newLISP in the real world / Re: Bug of (context Foo)?
November 02, 2013, 05:53:43 AM
I see, great thanks!



Foo introduced the "Foo" as a symbol with value of nil.

and (context Foo) also implicit introduce the symbol "Foo", although throw a error

"ERR: symbol or context expected in function context : Foo",



Is it right?



I should to read the source of newLisp I think.
#4
newLISP in the real world / Re: Bug of (context Foo)?
November 02, 2013, 04:25:09 AM
Please see detailed the following code and is there any issue?


Code Select

> (set 'Foo1:var1 nil)
nil
> (context? Foo1)
true
> (context Foo2)

ERR: symbol or context expected in function context : Foo2
> (set 'Foo2:var2 nil)

ERR: context expected in function set : Foo2
> (context? Foo2)
nil
> (set 'Foo2:var2 nil)

ERR: context expected in function set : Foo2

> (context? Foo2)
nil

>

Thanks for your reply. I think you are not understand my true ideas.



Before I define context Foo1, Foo1 is nil. (set 'Foo1:var1 nil) will surely define the Foo context,

then (context Foo1) is ok and (context2 Foo2) will return true.

See Foo2, It is also not defined, (context? Foo2) is nil and (context Foo2) will show errors. then

how can I define the Foo2 just after (context Foo2) which make some error?

(set 'Foo2:var2 nil) will always failed. This is my messes! If Foo2 has even not defined and you

evaluate (context Foo2) with some error, you will never define the context Foo2 by

"(set 'Foo2:var2 nil)". So I think it's a bug, perhaps!



I come from china, I love lisp but my english is a little bad, thanks your guys!
#5
newLISP in the real world / Re: Bug of (context Foo)?
November 01, 2013, 11:54:04 PM
I am not forgot the quote, I just do that.



Because (context Foo) is the first code line.  It's surely failed.

The question is once that code be evaluted, I wonder why the (set 'Foo:name nil) also will be failed.

but in a new clean newlisp instance, the (set 'Foo:name nil) will be ok without evaluated (context Foo).
#6
newLISP in the real world / Bug of (context Foo)?
November 01, 2013, 09:21:35 AM
the code
Code Select

(set 'Foo:name "limux")
(context Foo)

is ok.



but
Code Select

(context Foo)
(set 'Foo:name "limux")

is bad.



I think the bug is if you run the "(context Foo)" first, then "(set 'Foo:name "limux")"

will always report error.



Great thanks for more details about context or demo code!
Pages1