Hi Matt,
I didn't know about GDS, but why don't you just try geiser? It interacts
very nicely with the repl, gives you a number of typical conveniences,
it's pretty well documented (and the docs are even funny :)) and it
integrates well with scheme-mode. Even the guile guide recommends it.
Cheers
Hi all,
there was a thread a couple of years ago in this list about TODOs for
reaching R7RS (small) compliance. Just out of curiosity, what is the
current (or planned) level of conformance? I've read some recent
announcements about changes in the reader that further align it with
R7RS but I'm not
Hi Nala,
> IMO, when you have lambda*, you never need define-method. Actually, I
> want to say, once you have such FP features, you don't need OOP
> anymore.
I really don't see classes and multimethods a la CLOS competing against
FP features. They are about certain ways of composing structures an
name :age age))
[Notice how more convolved implementing the same using initialize would be]
-
In addition to this, you'd use a factory function, rather than having
the client call make-instance, to hide the CLOS nature of the type.
On Sep 3, 2014 1:47 PM, "Marko Rauhamaa&qu
> directly call initialize? In any case, why is this so? Wouldn't it be
> better for initialize to just get the "unpacked" argument list? This
> perplexes me.
I've been thinking about this, and lurking at the tinyclos
implementation, and then reading the cltl sections about initialization
in clos.
Thank you very much, Dave!
> Couldn't you just use (error)? It will enter the debugger if run from
I'm doing exactly that, but then there is the limitation that this
would be postmortem debugging and sometimes I want to suspend
execution, examine the environment, and *resume* execution.
Cheers
Hi all,
I've some questions about parameter handling in goops methods:
1) initialize takes the initargs argument as a list, because of the
way make-instance is defined. But the documentation states:
In theory, initarg … can have any structure that is understood by
whatever methods get applie
Hi all, although I have some experience with lisps, I'm still new to
guile and I'm having some trouble figuring out how to invoke the
interactive debugger at some arbitrary point in my code. Something like:
; code here
(debug)
; more code here
The closer solution I could f
> I'll give a try to the package in gna + 1.8.0, as
> you suggest.
Mhhh, same problem:
> ERROR: Unbound variable: read-and-dispatch-commands
> ABORT: (unbound-variable)
I'm using guile 1.8.0 and guile-debugging-0.12 (ie
latest from gna).
read-and-dispatch-commands is defined by
command-loop.sc
> > Would guile-debugging be eventually merged with
> guile core?
>
> Yes, this is in progress right now. I don't think
> it will be in time
> for the next stable release (1.8.1), though.
Great! I've tried the CVS version, but throws some
errors when debug-trapping (quoted below), so I guess
I'
guile-debugging gna project.
What is the way to go? This is pretty confusing for a
newcomer like me. Would guile-debugging be eventually
merged with guile core? Perhaps the manual should be
updated, shouldn't it? Anyway, how is a breakpoint
established?
Best regards,
Carlos
--- Carlos P
Hi all!
I've just installed guile-1.8 (stable) but I'm not
able to import the ice-9 debugger breakpoints module
as the reference manual suggests (in fact, the module
isn't there):
(use-modules (ice-9 debugger breakpoints))
Backtrace:
In current input:
1: 0* (use-modules (ice-9 debugger break
12 matches
Mail list logo
