Hi Bruce, Bruce Korb <bk...@gnu.org> skribis:
> On 01/03/12 15:33, Ludovic Courtès wrote: >> Could you point me to the affected code? What would you think of using >> string-copy as I suggested? The disadvantage is that you need to modify >> your code, but hopefully that can be automated with a sed script or so; >> the advantage is that it would work with all versions of Guile. > > The disadvantage is that I know I have "clients" that have rolled their > own templates, presumably by copy-and-edit processes that will invariably > include (define var "string") syntax. If the users files are evaluated rather than compiled/loaded, this is not a problem: scheme@(guile-user)> (eval (call-with-input-string "(define foo \"sdf\")" read) (interaction-environment)) $9 = #<variable 32a8580 value: "sdf"> scheme@(guile-user)> (string-set! (variable-ref $9) 1 #\x) scheme@(guile-user)> (variable-ref $9) $10 = "sxf" Could you check whether this is the case? In case it’s not, I have another possible solution in mind. ;-) > I'm sorry about being irritable. This is the third problem with 2.x. Yeah, I understand it can be really annoying and frustrating. Believe me, despite the breadth and depth of changes between 1.8 and 2.0, we did our best to avoid such nuisances. Hopefully we can help solve them with you, so you can really benefit from 2.0 (it’s a significantly nicer piece of software!) Thanks, Ludo’.
