I should mention that credit goes mostly to Alex Shinn and only some of it
to me. And yes, giving an explicit PLATFORM always works; this code is
triggered only if PLATFORM is not defined. As opposed to empty, in which
case you get, as an artifact of how it's implemented, the good old "Set
> Hi Peter,
>
> On 12/28/19 4:42 PM, Peter Bex wrote:
> > I think we're about ready to start the process for a 5.2.0
> > release. What do you think? Should we wait for the eggs
> > from #1655 to be fixed?
> >
> > What about the plaform auto-detection patch?
>
> IMO we should try to fix the eggs
Hi Peter,
On 12/28/19 4:42 PM, Peter Bex wrote:
I think we're about ready to start the process for a 5.2.0
release. What do you think? Should we wait for the eggs
from #1655 to be fixed?
What about the plaform auto-detection patch?
IMO we should try to fix the eggs but wait until after a
Hi all,
I think we're about ready to start the process for a 5.2.0
release. What do you think? Should we wait for the eggs
from #1655 to be fixed?
What about the plaform auto-detection patch?
Cheers,
Peter
signature.asc
Description: PGP signature
On Thu, Dec 19, 2019 at 11:19:16AM -0500, John Cowan wrote:
> Here's the second patch I mentioned on #chicken.
Hi John,
I've tried these two patches, but found several problems with them:
- The endif in the second patch is misplaced, so on UNIX, platform
detection was skipped completely.
On Sun, Dec 22, 2019 at 11:09:12AM +0100, felix.winkelm...@bevuta.com wrote:
> Hi!
>
> "-:hs0" is currently ineffective, since validity checks between parsing
> the option and initializing the heap overwrite the setting.
>
> This patch initializes the heap-parameter variables statically,
>
