From mboxrd@z Thu Jan 1 00:00:00 1970 References: <87v9xbih63.fsf@kyleam.com> From: Ricardo Wurmus Subject: Re: Some doc/examples files incompatible with latest update Message-ID: <87d0jj9m4s.fsf@elephly.net> In-reply-to: <87v9xbih63.fsf@kyleam.com> Date: Wed, 12 Jun 2019 11:41:59 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable To: Kyle Meyer Cc: gwl-devel@gnu.org List-ID: Hi Kyle, > Playing around with the latest updates (specifically on commit 08ccba0), > I'm unable to run some of the examples. Sorry for the breakage. I wasn=E2=80=99t done with implementing proper err= or handling and reporting. > | ERROR: In procedure scm-error: > | No applicable method for #< workflow-processes* (1)> in call > | (workflow-processes* #) =E2=80=9Cload-workflow=E2=80=9D now prints an understandable error message = when the file it loads does not evaluate to a workflow. > The warning on the first line seems to be spurious---simple.scm doesn't > use "restrictions"---and I'd guess that warning was introduced by > 8e76f22 (workflows: Implement type with GOOPS). That was indeed a side-effect of initializing the =E2=80=9Crestrictions=E2= =80=9D field to #F. This is now fixed. > I'm still not able to get extended-example-workflow.scm running despite > d676e60 already adjusting it. I've debugged it a bit, and there seems > to be a few separate issues, but I didn't get it working and I'm running > out of time at the moment to properly write it up, so I'll leave it be > for now. The problem appeared to be the conflicting import of =E2=80=9Czip=E2=80=9D = from (gnu packages compression) and (srfi srfi-1), which is loaded by default. It=E2=80=99s also fixed now. -- Ricardo