Pike-devel June 2008

pike-devel@lists.lysator.liu.se

9 participants
23 discussions

_main call OCPikeInterpreter.m
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 05 Jun '08

05 Jun '08

I've just committed a fix so that putenv and getenv actually do what they claim to do. As part of this, master()->_main no longer takes an environment mapping. I think I've made the corresponding change for that in OCPikeInterpreter.m too, but someone who knows what's going on there better take a look at it, because to me the call to master()->_main seems to be missing altogether.

2 2

7.8 blockers
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 01 Jun '08

01 Jun '08

For Tools.Standalone.dump constant dont_dump_program=1 is a solution.

1 0

Setting things to NULL after free
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 01 Jun '08

01 Jun '08

It's been customary to set pointers to NULL after freeing them in object (and module) exit functions. I'd like to question whether that really makes much sense. The object storage is only going to be freed just afterwards anyway (same goes for dynamically loaded modules), so the only bugs that this kind of "hygiene" could help nail is if destruct_object or exit_dynamic_load misbehaves. That's a bit unlikely by now, and anyway it's an awful lot of code everywhere just for that. The assignments are not even inside #ifdef PIKE_DEBUG as such belts-and-suspenders things usually are. Or am I missing something here? Also, when a pointer is not supposed to be used anymore, I usually do something like this instead: free (x->foo); #ifdef PIKE_DEBUG x->foo = (void *) (ptrdiff_t) -1; #endif That is more likely to trig a helpful coredump if the pointer is being used incorrectly.

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 June 2008