Re: Build transient value on the fly

2014-08-15 Thread Christophe Gragnic
Dear list, some updates about my problem. I eventually decided to do the things The Good Way. Adding a shortcut to EmuLisp was a fun hack, almost a joke, but not a good idea as: 1) It was not EmuLisp anymore. 2) I may need this export functionality with other platforms (read PicoLisp implementatio

Re: Build transient value on the fly

2014-07-29 Thread Christophe Gragnic
Le 29 juil. 2014 10:40, a écrit : > > Why not redefine function Afficher? > [...] > Would that be an idea? But this IS the idea I'm trying to explain!!! The problem was to also redefine transient symbols, dynamically. chri

Re: Build transient value on the fly

2014-07-29 Thread andreas
Why not redefine function Afficher? Have one file in which Afficher has the original functionality, and another file were it instead produces this bockly XML ? Then you write your simple program in a third file, and depending on which of the other two files you (load), it runs or it produces XML.

Re: Build transient value on the fly

2014-07-28 Thread Christophe Gragnic
On Mon, Jul 28, 2014 at 9:11 PM, Tomas Hlavaty wrote: > > I can't make sense of what you are trying to achieve. Why do you want > to use transient symbols? Why not use normal interned symbols? How > does your use case differ? Do you have a simple example? Suppose you embed a DSL in Picolisp,

Re: Build transient value on the fly

2014-07-28 Thread Tomas Hlavaty
Hi Christophe, > No problem for Display, but "hello" should spontaneously have its value > changed to some XML containing the string "hello". >> >> in other words, you want to use the transient symbol "hello" as a >> variable? What is preventing you? > > The problem is that I would like t

Re: Build transient value on the fly

2014-07-28 Thread Christophe Gragnic
On Mon, Jul 28, 2014 at 9:27 AM, Tomas Hlavaty wrote: > Hi Christophe, > No problem for Display, but "hello" should spontaneously have its value changed to some XML containing the string "hello". > > in other words, you want to use the transient symbol "hello" as a > variable? What is p

Re: Build transient value on the fly

2014-07-28 Thread Tomas Hlavaty
Hi Christophe, >>> No problem for Display, but "hello" should spontaneously have its value >>> changed to some XML containing the string "hello". in other words, you want to use the transient symbol "hello" as a variable? What is preventing you? It's often done in PicoLisp. (let "hello" 123

Re: Build transient value on the fly

2014-07-27 Thread Christophe Gragnic
On Sun, Jul 27, 2014 at 3:09 PM, Tomas Hlavaty wrote: > Hi Christophe, Hi. As I tried to explain in this sentence: >> No problem for Display, but "hello" should spontaneously have its value >> changed to some XML containing the string "hello". I had no problem with functions (I used a simple «d

Re: Build transient value on the fly

2014-07-27 Thread Tomas Hlavaty
Hi Christophe, > If I sum up (efficiently) my problem, I need a program like: > > (Display "hello") > > to have two interpretations. > In the first context it would (surprise surprise) «println "hello"». > In the second context it should be reprogramed to generate some XML. > No problem for Displa

Re: Build transient value on the fly

2014-07-27 Thread Christophe Gragnic
On Sun, Jul 27, 2014 at 8:05 AM, Alexander Burger wrote: > Hi Christophe, Hi. > Thinking about it (again), it occurs to me that this description in some > way matches the behavior of _external_ symbols. These also may change > their value (and properties) «spontaneously». > > Perhaps you can tak

Re: Build transient value on the fly

2014-07-26 Thread Alexander Burger
Hi Christophe, > > Hmm, so is this the same as the localization does in PicoLisp? > > Quite the same, except that we don't have a list of all messages to > translate. Any transient, even an unexpected one, should > «spontaneously» have its value transformed by a function > when retrieved. Thinki

Re: Build transient value on the fly

2014-07-25 Thread Christophe Gragnic
On Fri, Jul 25, 2014 at 4:53 PM, Alexander Burger wrote: > I see. This is not possible, because the fetching of a symbol's value > happens at the very lowest level of the interpreter (in fact it is only > a single machine instruction), and can't be changed from the outside. > And if you'd change t

Re: Build transient value on the fly

2014-07-25 Thread Alexander Burger
Hi Christophe, > > Hmm, so is this the same as the localization does in PicoLisp? > > Quite the same, except that we don't have a list of all messages to > translate. Any transient, even an unexpected one, should > «spontaneously» have its value transformed by a function > when retrieved. I see.

Re: Build transient value on the fly

2014-07-25 Thread Christophe Gragnic
On Fri, Jul 25, 2014 at 12:00 PM, Alexander Burger wrote: > Hi Christophe, Hi Alex. > Hmm, so is this the same as the localization does in PicoLisp? Quite the same, except that we don't have a list of all messages to translate. Any transient, even an unexpected one, should «spontaneously» have

Re: Build transient value on the fly

2014-07-25 Thread Alexander Burger
Hi Christophe, > Is it possible to shortcut the value resolution of transient > symbols with a custom function? Something like: I'm not sure I understand the question. The value of symbols (not only transients) is the CDR of the cell representing the symbol. The evaluator of the interpreter fetc