<Regenaxer>
Wow, impressive! *Lots* of native calls!
<Regenaxer>
Where is 'plio' defined?
<tankf33der>
functions.l
<Regenaxer>
'pliopr' uses pipe
<tankf33der>
yea.
<tankf33der>
its ok.
<tankf33der>
as is.
<Regenaxer>
I cannot find 'plio'
<tankf33der>
you find plio in test.l, right ?
<Regenaxer>
yep
<tankf33der>
its wrong, checking.
<Regenaxer>
source version mismatch?
<tankf33der>
yea
<tankf33der>
fixed.
<tankf33der>
no plio anymore
<Regenaxer>
Great :)
<tankf33der>
already inside decr
ubLIX has joined #picolisp
ubLIX has quit [Remote host closed the connection]
ubLIX has joined #picolisp
<razzy>
are there any difference between symbol and variable? from output point of view? did they differ internaly from the speed of processing point of view?
<razzy>
i would love if there is no difference
<Regenaxer>
They are *completely* different
<Regenaxer>
and have nothing to do with "output"
<Regenaxer>
They are different concepts
<razzy>
Regenaxer: in repl they behave the same (as i can verify)
<Regenaxer>
A symbol is a data type
<Regenaxer>
Variables are places where a value is stored
<razzy>
Regenaxer: do they differ internaly in proccesing? i bet they could be different because compilation
<Regenaxer>
The question is wrong
<Regenaxer>
they can't "differ internaly in proccesing"
<Regenaxer>
Variables don't exist internally
<Regenaxer>
they are a concept
<razzy>
Regenaxer: so they are completelly the same from computer view, yes?
<Regenaxer>
Only symbols exist in pil
<Regenaxer>
A variable may be a symbol or the CAR of a list
<razzy>
functions are important for compilers :]
<razzy>
functions/variables distinction are important for compilers
<razzy>
ah soo classes are property of symbol,.. nice
jibanes has quit [Ping timeout: 268 seconds]
jibanes has joined #picolisp
<Regenaxer>
razzy, not completely correct. Classes *are* symbols, with methods and superclasses in the value
ubLIX has quit [Quit: ubLIX]
orivej has quit [Ping timeout: 245 seconds]
orivej has joined #picolisp
<razzy>
i know you named tag something in coroutines. but i always thinked about property list as a list of "tags" (my stupid name).
<razzy>
so is my statement right? one symbol could have many properties. one property could have many symbols. and symbols could inhereted some other symbol property :?
<Regenaxer>
yes, the keys of properties might perhaps be called "tags" (though I use that term only for catch/throw and coroutines)
<Regenaxer>
Properties are key/value pairs
<Regenaxer>
and a symbol can have an arbitrary number of properties
<Regenaxer>
They are not inherited normally, inheritance is only in OOP, and there only for behavior (methods), not data
<razzy>
i still study the difference
<razzy>
between methods and data
<Regenaxer>
Methods are like functions, but dynamically dispatched at runtime depending on the class of that object
alexshendi2 has quit [Quit: Yaaic - Yet another Android IRC client - http://www.yaaic.org]