Pike-devel March 2010

pike-devel@lists.lysator.liu.se

6 participants
15 discussions

Start a nNew thread

7.8.406 alpha
by Peter Bortas ＠ Pike developers forum 11 Mar '10

11 Mar '10

New build: http://pike.ida.liu.se/download/pub/pike/alpha/7.8.406/ No windows build avilable.

5 17

Hi All, , , I get a lot of 'Cannot access global variables in destructed object' errors when rebooting Roxen. It looks as though a function call is completed even after the object is destructed. I only get the error when setting (private) class members of an object. The rest of the functions seems to execute without problem., , Is there any way to prevent this? Like either not execute the function if the object is (going to be) destructed or not destruct an instance until the function has completed?, , Than
by Coen Schalkwijk 08 Mar '10

08 Mar '10

Hi All, I get a lot of 'Cannot access global variables in destructed object' errors when rebooting Roxen. It looks as though a function call is completed even after the object is destructed. I only get the error when setting (private) class members of an object. The rest of the functions seems to execute without problem. Is there any way to prevent this? Like either not execute the function if the object is (going to be) destructed or not destruct an instance until the function has completed? Thanks in advance!* * -- Met vriendelijke groet / With kind regards / mit besten Grüßen, Coen Schalkwijk Software Engineer coen.schalkwijk(a)rtl.nl <mailto:coen.schalkwijk@rtl.nl> coen(a)rtlinteractief.nl <mailto:coen@rtlinteractief.nl> +31 (0)35 671 8915

1 0

08 Mar '10

1 0

Re: Feedback (Re: pcvs2git.pike)
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 01 Mar '10

01 Mar '10

In svn, a change in a keyword value does not count as a change; the file does not indicate as modified and the result of "svn diff" is empty.

4 7

port.c does not work in CONFIGURE_TEST mode?
by Stephen R. van den Berg 01 Mar '10

01 Mar '10

On eureka-git.lysator.liu.se: --------------------- $ make configure [...] checking if union initialization works... yes checking if port.c works in CONFIGURE_TEST mode... no configure: error: port.c does not work in CONFIGURE_TEST mode. This is an internal problem in Pike. configure aborted since further configure tests will be unreliable. gmake: *** [configure] Error 1 --------------------- Is this a known issue? Any suggestions? -- Sincerely, Stephen R. van den Berg. I'm NaN.

2 2

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 March 2010