🚀 go-pugleaf

Robert,

I am gratified to see you are acknowledging that a problem exists with
the patch, and that the workaround will be documented.  However, what
would send me over the top into spasms of ecstasy would be some kind of
statement from you or your organization that a patch for the patch, or a
revision of the original patch is forthcoming and when we can reasonably
expect it.

Workarounds are, at best, temporary measures and frankly I don't have the
time to modify code produced by a generator - I have problems enough with
the stuff I write!

Regards,
John

aphrael@magescave.blackforest.org wrote:

> In article <379F380B.A39BBB1C@artisansoftware.com>,
> Steve Pietrykoski  <steve@artisansoftware.com> wrote:
> >> Note that there should be no problem whatsoever with completely
> >> new projects: i've tested about a dozen now, and all of them
> >> have worked flawlessly. The problem only exists in projects
> >> taken from the unpatched version to the patched version.
> >
> >Robert,
> >
> >As you've seen in my other post in this thread, there is another bug
> >that you've given me a workaround for.  But that bug affects *every*
> >project, new or otherwise, does it not, and is therefore a bit more
> >serious?
>
> The problem here is that the code generator for the implementation
> file generates code which must be manually edited to include a
> cast, right? I'll grant that is a bug ... but all I can do at the
> moment is guarantee that the workaround gets documented.
>
> --
> Caminante, son tus huellas el camino, y nada mas;
> caminante, no hay camino, se hace camino al andar ...
> Caminante, no hay camino, sino estelas en el mar.