Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

Hohum
by Per Hedbor () ＠ Pike (-) developers forum 09 Nov '03

09 Nov '03

aido/pike-modules/GLUE.pmod/module.pmod:1242:Wrong return type. aido/pike-modules/GLUE.pmod/module.pmod:1242:Expected: { BaseTexture = object(implements 65701) } aido/pike-modules/GLUE.pmod/module.pmod:1242:Got : object(is 65735) aido/pike-modules/GLUE.pmod/module.pmod:1242:Type of identifier "texture_type" does not match. aido/pike-modules/GLUE.pmod/module.pmod:1242:Expected: int(34382..34382) aido/pike-modules/GLUE.pmod/module.pmod:1242:Got : int(3553..3553) aido/pike-modules/GLUE.pmod/module.pmod:1310:Class definition failed. Eh, yes? I want to have different constant values in my different classes. That was the whole point of that specific constant.

1 0

| on arrays
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 09 Nov '03

09 Nov '03

I have a feeling this probably has been discussed before, but please refresh my memory in that case. When | is used on arrays, all elements that occurs in both follows the order in the second operand: > ({1,2}) | ({2,1}); (1) Result: ({ /* 2 elements */ 2, 1 }) This has surprised users on several occasions, and it's also at odds with how & handles it: > ({1,2}) & ({2,1}); (2) Result: ({ /* 2 elements */ 1, 2 }) The old tutorial says that the order is taken from the left argument, but afaics it has never been that way for |. So I think the behavior in | is a bug and would like to fix it (maybe with compat provisions). But I see there's a test in the testsuite that appears to test this very consciously: test_equal( ({1,2,3,4,4}) | ({3,5,6}), ({1,2,4,4,3,5,6})) So before I go ahead and break something, I'd like to if there's a thought behind it and what it is in that case.

2 1

configure error in DVB module
by Niels M�ller (igelkottsr�ddare) ＠ Pike (-) developers forum 09 Nov '03

09 Nov '03

I'm trying to build pike/7.5 from CVS. I'm using autoconf-2.57. The generated configure script contains # So? What about this header? case $ac_header_compiler:$ac_header_preproc in yes:no fi which leads to syntax error when running it. Perhaps it's the recursive use of AC_CHECK_HEADERS dnl Checking for version 2+ API AC_CHECK_HEADERS(linux/dvb/version.h, [ AC_CHECK_HEADERS(linux/dvb/sec.h, [PIKE_FEATURE(DVB,[yes (version 2 api)])], [PIKE_FEATURE(DVB,[no (missing linux/dvb/sec.h - version 3 api?)]) ]) ]) that for some reason won't work. For now, I just replaced the tests with a PIKE_FEATURE(DVB,[no (disabled)]) to be able to compile.

1 0

Unsynched stack
by Martin Nilsson (saturator) ＠ Pike (-) developers forum 08 Nov '03

08 Nov '03

When running hilfe in a dmalloc Pike with -d3 it gets a fatal telling me /home/nilsson/Pike/7.5/src/interpret_functions.h:1058: Fatal error: Stack out of synch - should be 55, is 76. [long list of pike opcodes] It sounds bad. Is it?

2 1

Hilfe strangeness
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 07 Nov '03

07 Nov '03

Pike v7.5 release 12 running Hilfe v3.5 (Incremental Pike Frontend) > _next((mixed)23414325134512341234); (1) Result: Tools.Hilfe.Expression(({ /* 8 elements */ "_next", "(", "(", "mixed", ")", "23414325134512341234", ")", ";" }))

2 2

README
by Martin Nilsson (saturator) ＠ Pike (-) developers forum 06 Nov '03

06 Nov '03

The Pike README (not to be confused with README-CVS) says that you need autoconf, m4 and bison to build a dist. Are those correct? I thought those were only needed when building from CVS or creating a source dist.

3 8

*** discount tobacco offer ***
by Marcus Agehall (Scanian) ＠ Pike (-) developers forum 04 Nov '03

04 Nov '03

Ok, how about filtering this list using spamassassin or something similar..? Two spams in one morning are two more than I want on this list... / Marcus Agehall (Scanian) Previous text: >2003-11-03 11:02: >Subject: *** discount tobacco offer *** >-------------------------------------------------------------------- >Dear sir or Madam, > If you are a smoker in the UK, ROI or Scandinavia, please just take a few minutes of your time to read this. > >If you are not a smoker please accept my apologies for this E mail, it is not my intention to upset anyone. > >Smokers - are you still paying high street prices for your cigarettes, cigars or rolling/pipe tobacco. > >For instance, I can send you by registered post, 800 cigarettes for 180 euros. > >This works out to about £3.20 a packet (depending on exchange rate). > >For this price, and it includes all brands (see note at bottom of page), they will be sent by registered post direct to your door. Just click on the >link below:- > >http://www.pennyround28 > >Yours faithfully > >A believer in the rights of the British Smokers > >P.S. >If this E at all offends you mail - that is not my intention ---- YOU WILL NOT BE E MAILED AGAIN > > >Brands supplied including:- B & H, Dunhill, Lamb & But, Silk Cut, Marlboro, JPS, Gitanes, Fortuna, Berkeley, Superkings, Embassy, Regal, St >Bruno, >Golden Virginia, Old Holborn, Samson, Clan, Vogue, MORE, Kent, Davidoff , Peter Stuyvesant, Gauloises, Sovereign, Lucky Strike, Havana, >Monte >Cristo, Flor de Cano, Rothmans, Camel etc. > > >http://www.pennyround28 > > > / Brevbäraren >

5 5

module build process
by Bill Welliver 31 Oct '03

31 Oct '03

I've checked in some changes to various portions of the module build code. It doesn't look like i've broken anything yet, but if everyone could keep an eye out for problems, that would be great. Also, while it seems to work well in the pike tree and for the very simple cases i've thrown at it, it doesn't yet install the modules it has prepared into the pike installation. It actually doesn't appear that the makefiles ever did that. Can someone comment on this situation? What was the plan for having pike -x module actually install the module it prepares? Thanks in advance! Bill

5 11

Re: Are strings generally limited?
by Mirar ＠ Pike developers forum 29 Oct '03

29 Oct '03

>> | Pike v7.5 release 12 running Hilfe v3.5 (Incremental Pike Frontend) >> | > Regexp.PCRE rx=Regexp.PCRE( "(\"([^\"\\\\]|\\\\.)*\")" ); >> | > rx->split( "\"" + "x"*0xE800 ); >> | zsh: segmentation fault pike > >Ouch. That lowered my esteem for PCRE quite a bit. It ought to be >reported to them. Yes, if it is a PCRE problem and not a Pike problem... But I can't see how it can be a Pike problem. Does Pike switch method somewhere depending on string length? / Mirar Previous text: >2003-10-27 12:49: >Subject: Re: Are strings generally limited? >-------------------------------------------------------------------- >Mirar <mirar-yg(a)mirar.org> wrote: > >> | Pike v7.5 release 12 running Hilfe v3.5 (Incremental Pike Frontend) >> | > Regexp.PCRE rx=Regexp.PCRE( "(\"([^\"\\\\]|\\\\.)*\")" ); >> | > rx->split( "\"" + "x"*0xE800 ); >> | zsh: segmentation fault pike >> >> Hmm? > >Ouch. That lowered my esteem for PCRE quite a bit. It ought to be >reported to them. > > > > / Brevbäraren >

4 7

Pike-Community: a new beginning
by Peter Lundqvist (disjunkt) ＠ Pike (-) developers forum 28 Oct '03

28 Oct '03

I guess that the index.html in the Pike Community group is a clue...

2 3

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