gcc 3.2
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum
06 Dec '02
06 Dec '02
Or even better: -pedantic-errors
1
0
*boggle*
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum
06 Dec '02
06 Dec '02
What's this? Why is case 2 different from the other three?
Pike v7.3 release 62 running Hilfe v3.5 (Incremental Pike Frontend)
> function plus = `+;
> `+(("hello world"/" ")[*]);
(1) Result: ({ /* 2 elements */
"hello",
"world"
})
> plus(("hello world"/" ")[*]);
Compiler Error: 1:[*] not supported here.
> array(string) hi = "hello world"/" ";
> `+(hi[*]);
(2) Result: ({ /* 2 elements */
"hello",
"world"
})
> plus(hi[*]);
(3) Result: ({ /* 2 elements */
"hello",
"world"
})
>
1
0
Core!
by Johan Sundstr�m (�rkehertig av Lysators rootgrupp) @ Pike (-) developers forum
06 Dec '02
06 Dec '02
I just found a pretty minimized test case for a coredump recipe:
pelix> pike -t2 -e ''
/pike/home/marcus/Pike/7.3/src/object.c:577: Fatal error:
Couldn't load master object.
No stack - no backtrace.
zsh: IOT instruction (core dumped) pike -t2 -e
-t1 works like a charm, though. :)
In the interest of getting the CHANGES worked out sooner or later I
will try to (with the eager help of members of this conferance) work
out at least one undescribed entry in the CHANGES per day. Depending
on current level of boredom there might be more than one entry in a
day.
1st entry:
basetype()
Suggested entry, added to "Language additions":
o basetype(foo)
Returns the basic type of foo as opposed to typeof(foo) that returns
the full type. Also available as sprintf("%t", foo).
This is, incidentally, also why I have not yet written a standard
function for this.
Take disk 'Gb':s as an example, they can be anything from 1024^3 to
1000^3 bytes, the most common size being 1000 * 1024^2 bytes.
Is it possible to have check_all_args and get_all_args to look up the
name of the current function if fname is null or something? The function
names are out of sync in more than one place, and performance isn't as
much of an factor since we only do this when there is an error.
I was wondering what the status of the 7.3 tree is. I have a simple
SNMP agent (~200 lines) I'd like to contribute to Protocols.SNMP, as
it makes that module more complete and demonstrates how to use
Protocols.SNMP.protocol. I didn't want to add it, because I've heard
rumors of a 7.4 release. Does anyone have any guidance about any of
this?
Thanks!
Bill
> access the numer of arguments, the actual arguments and the
^^^^^
1
0
7.3 -> 7.4
by Johan Sundstr�m (ska bli kalif i st�llet f�r kalifen) @ Pike (-) developers forum
05 Dec '02
05 Dec '02
Comments, AIEE!s and other thoughts about this (Nilsson and I trying
to remember what should be done and figure out a good way to do so):
# in the raw repository:
> mv 7.3 7.4
# elsewhere:
> cvs co Pike/7.4
> cd Pike/7.4
> cvs tag -R pre73to745split
# back in the reposityory:
# remove empty directories
> mv 7.4/README.txt 7.4/README
> mv 7.4/README.cvs.txt 7.4/README.cvs
> cp -rp 7.4 7.5
# finish 7.4/CHANGES
# clean up 7.5/CHANGES
# (tell someone to update their rsync settings)
# rerun CL indexer (since raw changes go unnoticed)
# make dists
# make announce