Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

Save_Object
by gmvalic＠cox.net 01 Mar '03

01 Mar '03

Coming from a LPC compiler background, is there anything within PIKE that would lean towards the save_object 'kfun' they have implemented in several compilers? What I am looking for is a function to take all the variables of an object and save them to a file. Vice-Versa there would be a function to load all those variables back into a cloned object. Anything or am I blowing smoke?

7 9

include directory, etc.
by Ryan Elgram 28 Feb '03

28 Feb '03

I noticed from other Pike programs you can send the -I switch to set your include directory. Is there any way to do this inside the pike program itself?

2 1

Parser.XML - The slow, the fat and the hungry :)
by Alexander Demenshin 28 Feb '03

28 Feb '03

Hi everybody, Is there any alternative to Parser.XML, accessible from Pike? Modules etc? Or are there any plans to rewrite it in C, possibly using something like libxml2? Perhaps someone may ask - what is wrong with Parser.XML?.. Well, it takes approximaly 20M RAM and 6 seconds to parse (only) 1M XML file (it contains approx. 80000 tags). This is a way too much, IMHO (libxml2 takes approx. 0.5s and only 4M RAM for same file - while this is not perfect too but more acceptable). Any ideas? Suggestions? Comments? Flames? :) Regards, /Al

5 4

Floating point (conversion) bug (affected: v7.4 & v7.5; may be Hilfe only)
by Mirar ＠ Pike developers forum 28 Feb '03

28 Feb '03

My theory was that it has something to do with double or better precision floats. But: > float f=1e99; > f*1e-99; (1) Result: 1.000000 Ok, jolly good. > 1e1000; (2) Result: 340282346638528859811704183484516925440.000000 Not so good. > 1e-99; (3) Result: 0.000000 > 1e-1000; Compiler Error: 1:parse error, unexpected TOK_IDENTIFIER, expecting TOK_LEX_EOF or ';' Huh?

12 84

Re: gcc/icc
by Mirar ＠ Pike developers forum 28 Feb '03

28 Feb '03

Well, it did compile, but when trying to link Pike it says, /tmp/iccbiNHGQOFas_: Assembler messages: /tmp/iccbiNHGQOFas_:2357: Error: symbol `..1.4_1.TAG.74.27.1082' is already defined /tmp/iccbiNHGQOFas_:2397: Error: symbol `..1.4_1.TAG.73.27.1082' is already defined /tmp/iccbiNHGQOFas_:2522: Error: symbol `..1.4_1.TAG.72.27.1082' is already defined /tmp/iccbiNHGQOFas_:2559: Error: symbol `..1.4_1.TAG.71.27.1082' is already defined ... instead. Is there any static assembler symbols generated with the same labels or something?

1 0

Save_Object
by David Hedbor ＠ Pike developers forum 27 Feb '03

27 Feb '03

Actually, perhaps there should be a construct similar to Java where you have to _make_ your object serializable (with a "implements Serializable"). Since a good default behaviour should save private variables, one might not want to make all objects serializable since that would essentially make the object all-public. Also in java there is an implicit (or explicit) version id of an object. That is a good idea too (the implicit one is sort-of a hash based on the variable types of the class or something along those lines).

1 0

Re: gcc/icc
by Mirar ＠ Pike developers forum 27 Feb '03

27 Feb '03

I thought I checked I didn't do anything stupid with diff first, but I must've been too sleepy. *reverts*

2 2

MIN_INT_TYPE
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 27 Feb '03

27 Feb '03

Mast, please commit your changes to global.h so that Pike 7.4 compiles again...

2 1

Re: gcc/icc
by Johan Sundstr�m (a hugging punishment!) ＠ Pike (-) developers forum 27 Feb '03

27 Feb '03

I'm referring to the change to configure.in around lines 1367 - 1371: # Currently only supported with gcc. # # Further tests later on. - with_machine_code="$GCC" + with_machine_code="yes" ])

2 1

Re: gcc/icc
by Mirar ＠ Pike developers forum 27 Feb '03

27 Feb '03

"/home/mirar/pike/src/bignum.c:169: undefined reference to `eval_instruction' ipo_iccbiRPr9vu.o(.text+0x224b):/home/mirar/pike/src/bignum.c:175: undefined reference to `eval_instruction' ipo_iccbiRPr9vu.o(.text+0x2366):/home/mirar/pike/src/bignum.c:185: undefined reference to `eval_instruction' ipo_iccbiRPr9vu.o(.text+0x244e):/home/mirar/pike/src/bignum.c:192: undefined reference to `eval_instruction' ipo_iccbiRPr9vu.o(.text+0x2650):/home/mirar/pike/src/interpret.c:1861: more undefined references to `eval_instruction' follow" Any ideas? ^.^

2 2

Jump to page:

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