Pike-devel January 2013

pike-devel@lists.lysator.liu.se

4 participants
14 discussions

pike --help=kladdkaka
by Hedda () ＠ Pike (-) developers forum 26 Jan '13

26 Jan '13

$ pike --help=kladdkaka Ingredients: 4 eggs 5 dl sugar 2 pinches salt 6 msk cocoa 200 g melted butter 3 dl wheat-flour 2 tsk vanilla sugar 1. Mix everything together 2. Pour into a greased circular form. 3. Bake in 175 degrees C (350 degrees F) for 1 hour. 4. Serve while it is still hot with whipped cream. ******************** It should say "6 tbs / 90 ml cocoa" and "2 tsp/10 ml vanilla sugar" otherwise it's hard to understand for non-Swedish people (Never mind that "kladdkaka" is 100% Swedish, but that's the name :P ).

7 15

overflow
by Arne Goedeke 06 Jan '13

06 Jan '13

I pushed a branch containing "hopefully" standard compliant overflow checks. Its in arne/of. I had to change a few places outside of bignum.h in order to get it all working with inlines. The switch from macro to inlines actually changed semantics, since the INT_TYPE_* macros were actually used both with int and unsigned int. Naturally, the inline functions fail to detect an overflow there, since INT_TYPE is 64 bit and calculations do not overflow. Maybe someone can try to compile and run verify on something other than amd64 with gcc? arne

6 21

git access
by H. William Welliver III 04 Jan '13

04 Jan '13

Can someone grant me the ability to push branches? I've got a few feature branches I'd like to get feedback on but I can't push them because they have slashes in them (I assume it's preferred that I not clutter the branch namespace unnecessarily.) Bill

2 1

More aggressive gc of weak mappings in Pike 7.9
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 01 Jan '13

01 Jan '13

Hi. I've now implemented the new rehash behaviour that we discussed during the conference ~2 months ago. This means that weak mappings that contain the only reference to a reference-counted object will free the object when the hashtable is resized. Note that this only takes care of the most common case of weak mappings. The more complicated cases will still need the full gc. For reference: INDEX INDEX VALUE VALUE HANDLING REFTYPE CONTENT REFTYPE CONTENT ------------------------------------------ STRONG * STRONG * KEEP STRONG * WEAK UNREF KEEP STRONG * WEAK SINGLE FREE STRONG * WEAK MULTIPLE KEEP WEAK UNREF STRONG * KEEP WEAK SINGLE STRONG * FREE WEAK MULTIPLE STRONG * KEEP WEAK UNREF WEAK UNREF KEEP WEAK UNREF WEAK MULTIPLE KEEP WEAK SINGLE WEAK * FREE WEAK * WEAK SINGLE FREE WEAK MULTIPLE WEAK UNREF KEEP WEAK MULTIPLE WEAK MULTIPLE KEEP Legend: STRONG Strong (default) reference. WEAK Weak (set with set_weak_flag()) reference. * Any value. UNREF Value that is not reference counted (eg ints or floats). SINGLE Reference-counted value with a single reference. MULTIPLE Reference-counted value with more than one reference. KEEP Entry to be kept after the rehash. FREE Entry to be freed during the rehash. I would appreciate testing, and any comments about the behaviour (intended or otherwise). Happy New Year! /grubba

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel January 2013