On pogo, after fixing the zNotStr instance:
...
PASS: loop.test
PATH is
On 06/17/12 23:26, Harlan Stenn wrote:
On pogo, after fixing the zNotStr instance:
...
PASS: loop.test
PATH is
On Mon, Jun 18, 2012 at 5:38 PM, Bruce Korb bruce.k...@gmail.com wrote:
On 06/17/12 23:26, Harlan Stenn wrote:
On pogo, after fixing the zNotStr instance:
...
PASS: loop.test
PATH is
On 06/18/12 10:57, Dave Hart wrote:
On Mon, Jun 18, 2012 at 5:38 PM, Bruce Korbbruce.k...@gmail.com wrote:
On 06/17/12 23:26, Harlan Stenn wrote:
On pogo, after fixing the zNotStr instance:
I have not seen Harlan's message about zNotStr,
so I don't know what the issue is.
That does not
On Mon, Jun 18, 2012 at 6:22 PM, Bruce Korb bruce.k...@gmail.com wrote:
On 06/18/12 10:57, Dave Hart wrote:
On Mon, Jun 18, 2012 at 5:38 PM, Bruce Korbbruce.k...@gmail.com wrote:
On 06/17/12 23:26, Harlan Stenn wrote:
On pogo, after fixing the zNotStr instance:
I have not seen Harlan's
Hi Dave,
You missed the point. I do not want two functions:
char const * fnc(char const * in)
as well as
char * fnnc(char * in)
any more than libc wants two flavors of strstr(), for example.
So strstr() returns char * and it is up to the caller to be careful.
Perhaps the right thing is to
On 06/18/12 11:22, Bruce Korb wrote:
I have not seen Harlan's message about zNotStr,
so I don't know what the issue is.
I've found the problem: It exists in an atrophied section of code
for Guile 1.6 only code. I've fixed it in my source now.
Since I don't have access to any platform with 6
Bruce wrote:
I've found the problem: It exists in an atrophied section of code
for Guile 1.6 only code. I've fixed it in my source now.
Since I don't have access to any platform with 6 year old Guile,
I have to depend on others to alert me during the pre release phase.
Guile 1.8 was
