Hellu!
>> Yes, you're right.
>> I even went a little further with that and now I also capture lexical
>> environment:
>> (use-modules (system syntax) (ice-9 local-eval))
>>
>> (define-macro (function args . body)
>> `(let ((environment (the-environment))
>> (lexical-names (lexical-names
Panicz Maciej Godek writes:
> The strange thing was that I had to define the macro ``function''
> using define-macro -- the define-syntax counterpart for some reason
> wouldn't work. So for example, if I wrote
> (define f (let ((y 5)) (function x (set! y (apply + y x)) y))
> then if ``function'' w
Hello!
Panicz Maciej Godek skribis:
> Well, the problem is that I don't yet know what I am doing, so I'm
> trying to keep the system as general as possible. One of the features
> that is certainly going to be needed anyway, is a way to store and
> restore lambdas, because this is the essential a
Howdie
> Instead of storing actual code that recreates the GUI, how about storing
> high-level declarations that describe that GUI?
[...]
Well, the problem is that I don't yet know what I am doing, so I'm
trying to keep the system as general as possible. One of the features
that is certainly goin
Hi,
Panicz Maciej Godek skribis:
> I recall someone having the idea of adding smalltalk-like images to guile.
> I'd love to see such feature one day, but if guile is supposed to be
> an extension language, I think the C interface would need to be
> redesigned, because there would be a need to so
Hi,
Panicz Maciej Godek skribis:
> Well, the idea for now is that the associated .spec file containing
> the state of GUI is loaded on startup, and the state of the
> interpreter is dumped to that file on exit (or at GUI's request).
> Viewing the file will obviously be an option (for the curious
> On 3 October 2012 03:29, Panicz Maciej Godek wrote:
>> Well, the idea for now is that the associated .spec file containing
>> the state of GUI is loaded on startup, and the state of the
>> interpreter is dumped to that file on exit (or at GUI's request).
>> Viewing the file will obviously be an
On 3 October 2012 03:29, Panicz Maciej Godek wrote:
> Well, the idea for now is that the associated .spec file containing
> the state of GUI is loaded on startup, and the state of the
> interpreter is dumped to that file on exit (or at GUI's request).
> Viewing the file will obviously be an option
>> The short answer is: to have more options to explore and play around with.
>> The long answer is that I have been designing a framework for rapid
>> GUI development (and more), sort of a REPL among GUIs. The sources are
>> available on bitbucket's mercurial, if you want to see:
>> hg clone https
Hi,
Panicz Maciej Godek skribis:
> The short answer is: to have more options to explore and play around with.
> The long answer is that I have been designing a framework for rapid
> GUI development (and more), sort of a REPL among GUIs. The sources are
> available on bitbucket's mercurial, if yo
>> I've found a bug report on savannah, which noted the lack of
>> ``procedure-source'' for guile 1.9.11
>> http://savannah.gnu.org/bugs/?30469
>> I wonder if any further decisions were made regarding the maintenance
>> of ``procedure-source''. I would find it really useful for my
>> application if
On 09/30/2012 04:11 PM, Panicz Maciej Godek wrote:
I've found a bug report on savannah, which noted the lack of
``procedure-source'' for guile 1.9.11
http://savannah.gnu.org/bugs/?30469
I wonder if any further decisions were made regarding the maintenance
of ``procedure-source''. I would find it
I've found a bug report on savannah, which noted the lack of
``procedure-source'' for guile 1.9.11
http://savannah.gnu.org/bugs/?30469
I wonder if any further decisions were made regarding the maintenance
of ``procedure-source''. I would find it really useful for my
application if the sexp containi
Hi,
I remember, that guile 1.8 had a meta-procedure called
'procedure-source' that returned what it said it would.
As I'm trying to use it now (with 2.0), it always returns #f.
Is there any way to convince guile to memoize the source
code of at least some of the procedures defined by user,
so they
14 matches
Mail list logo
