Re: 2.20 plans.

[Phil Holmes]

----- Original Message ----- 
From: "David Kastrup" <address@hidden>
To: "Phil Holmes" <address@hidden>
Cc: <address@hidden>
Sent: Tuesday, October 16, 2018 9:11 PM
Subject: Re: 2.20 plans.


> "barf" sounds like an intentionally undefined function, "called" in
> order to get a backtrace.
>
> When I learnt programming, long long ago in the time of punch cards, my
> mentor used "CALL HUGO" for this purpose.  Indeed this triggered a
> _runtime_ error on the Fortran 77 compiler of the Cyber 175.
>
> I guess this is the same trick, just for Python.  So now we have a
> backtrace.  We just need to figure out what reason "barf" is getting
> called for.  What's in line 707 of repository.py ?
>
> --
> David Kastrup

Barf has always been part of the GUB build system - it's called when 
something goes wrong - see the earlier error when it says "Command barfed" 
to show what happened when the git call failed.  So why it should suddenly 
stop working is beyond me.

--
Phil Holmes