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

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-29 Thread Christophe Gragnic
Le 29 juil. 2014 10:40, andr...@itship.ch 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-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 (println

Re: Build transient value on the fly

2014-07-28 Thread Christophe Gragnic
On Mon, Jul 28, 2014 at 9:27 AM, Tomas Hlavaty t...@logand.com 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

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 to avoid maintaining a

Re: Build transient value on the fly

2014-07-28 Thread Christophe Gragnic
On Mon, Jul 28, 2014 at 9:11 PM, Tomas Hlavaty t...@logand.com 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

Re: Build transient value on the fly

2014-07-27 Thread Christophe Gragnic
On Sun, Jul 27, 2014 at 3:09 PM, Tomas Hlavaty t...@logand.com 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

Build transient value on the fly

2014-07-25 Thread Christophe Gragnic
Hi, The technical/dry question: Is it possible to shortcut the value resolution of transient symbols with a custom function? Something like: (de shortcut_transient (name) (pack name !)) This would add a ! to the default value of a transient sym. If I had to answer, I'd say «no», but PicoLisp is

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

Re: Build transient value on the fly

2014-07-25 Thread Christophe Gragnic
On Fri, Jul 25, 2014 at 12:00 PM, Alexander Burger a...@software-lab.de 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

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. This