hi,
i am reviewing the pike entry on wikipedia and noticed that the logo
image lacks clear license information. while trying to find out what the
actual license is i found that there is no clear information on the pike
website either.
i think it would be helpful if http://pike.ida.liu.se/about/pike/
contained a phrase like: the pike name and logo are registered
trademarks of IDA.
i would also like to clarify the license of the logo images on
http://pike.ida.liu.se/download/logotype/
i …
[View More]believe there is no problem with making them gpl or mpl since they
are protected by a trademark anyways.
are there any issues with adding these clarifications on the pike site?
greetings, martin.
[View Less]
Hi,
Is it possible to add a comment to a GIF file with the Image.GIF
library? (using pike 7.4) If this is possible at all, does anyone have
some sample code?
--
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
__________________________________________________________
Deze e-mail en …
[View More]de inhoud is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail verzoeken wij u dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken.
The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system.
__________________________________________________________
[View Less]
I noticed this problem when using pike -M in 7.6 and I guess its known,
since it does not occur anymore in pike 7.8. Consider this situation:
one has some module directory and a class from that module is used
somewhere in module.pmod. Using these examples
* dir/module.pmod
string h(int i) {
return .A()->h(i);
}
* dir/A.pike
string h(int i) {
return String.int2char(i);
}
Now, when using pike -M dir/ I get the following error:
dir/A.pike:2:Got placeholder object (resolver problem) …
[View More]when resolving
'String'.
dir/A.pike:2:Undefined identifier "String".
dir/A.pike:2:Got placeholder object (resolver problem) when resolving
'String'.
dir/A.pike:2:Undefined identifier "String".
dir/module.pmod:2:Error looking up 'A' in module '.'.
Attempt to call the NULL-value
Unknown program: 0()
The problem goes away either by using A() instead of .A() or by using
pike -M dir without the "/". Is this a bug or am I doing something wrong
here?
arne
[View Less]
Would replace(string, array(string), array(string), mapping(string:int))
be a useful/convenient interface for the following functionality?:
I'd like the 4th argument mapping to be filled by the replace function
to tally the number of times it has found and replaced the corresponding
string.
It is difficult at best to obtain that information (efficiently) otherwise,
especially when some of the strings fit in the prefix of some of the others.
The actual use case for me is the bindings parser …
[View More]for pgsql, which preferably
needs to eliminate any unused variables before constructing the query to
be sent to the database.
The reason I'm looking at this is because I just had an occurrence of
a binding called ":telno" and ":telnopriv", whereas the :telno wasn't present,
but the :telnopriv was. Quick checks with has_value() break down in this
case, because :telno is found as a prefix of the actually occurring :telnopriv,
obviously.
Any alternate ideas which solve this problem are welcome, of course.
--
Sincerely,
Stephen R. van den Berg.
"Having a non-smoking section in a restaurant is like
having a non-peeing section in a pool."
[View Less]
Kai Voigt wrote:
>a stored procedure in MySQL doesn't return anything itself, but it
>might include one or more SQL statements which are returned to the
>calling client as if those statements would have been called
>individually.
>Note that you might have to handle multiple statements in a stored
>procedure.
I see.
So I presume that stored procedures in MySQL are not invoked through
mere SELECTs?
It would imply, though, that if you stick to at most one SELECT …
[View More]resultset
in your MySQL stored procedure, then the current Sql interface in Pike
will/should suffice.
Oracle and PostgreSQL can return at most a single resultset, and are invoked
through SELECT normally.
--
Sincerely,
Stephen R. van den Berg.
"<Clarions sounding> *No one* expects the Spanish inquisition!"
[View Less]
Is there a particular reason this doesn't work:
Pike v7.8 release 127 running Hilfe v3.5 (Incremental Pike Frontend)
> Stdio.FILE in;
> (in=Stdio.FILE())->assign(Stdio.FakeFile("foo\nbar\n"));
Stdio.File(): not open.
/usr/local/pike/7.8.127/lib/modules/Stdio.pmod/module.pmod:1490:
Stdio.FILE(0, 0, 777 /* fd=-1 */)->set_read_callback(0)
/usr/local/pike/7.8.127/lib/modules/Stdio.pmod/module.pmod:1192:
Stdio.FILE(0, 0, 777 /* fd=-1 */)->set_read_callback(…
[View More]0)
/usr/local/pike/7.8.127/lib/modules/Stdio.pmod/module.pmod:727:
Stdio.FILE(0, 0, 777 /* fd=-1 */)->assign(Stdio.FakeFile(8,"rw"))
/usr/local/pike/7.8.127/lib/modules/Stdio.pmod/module.pmod:1776:
Stdio.FILE(0, 0, 777 /* fd=-1 */)->assign((a)0=Stdio.FakeFile(8,"rw"))
>
--
Sincerely,
Stephen R. van den Berg.
I'm sorry. The number you have reached is imaginary.
Please rotate your phone 90 degrees and try again.
[View Less]
Arne Goedeke wrote:
>Stephen R. van den Berg wrote:
>>> Stdio.FILE in;
>>> (in=Stdio.FILE())->assign(Stdio.FakeFile("foo\nbar\n"));
>> Stdio.File(): not open.
>Not sure what you expect it to do. Stdio.File operates on an fd,
>FakeFile does not have any. I think that assign is meant to be used for
>Stdio.File subclasses primarily.
Well, I'd like to have a FakeFile() with getchar(), gets() and unread().
So I thought, opening a Stdio.FILE() with a FakeFile()…
[View More] as source should
do the trick.
--
Sincerely,
Stephen R. van den Berg.
The first 90% of code accounts for the first 90% of development time.
The remaining 10% of code accounts for the other 90% of development time.
[View Less]
Pike 7.8 currently does:
> ({"abc",({65,65,66}),"def"})*"x";
(1) Result: "abcxdef"
I have created a patch that makes it do:
> ({"abc",({65,65,66}),"def"})*"x";
(1) Result: "abcxAABxdef"
instead, and which also throws an error if any other types are inside
the array (the old code merely skipped them).
I'd consider the second behaviour (after my patch) more desirable and
in light of actually throwing errors on unsupported types, it is really
is a bugfix.
Any objections to this behaviour?…
[View More]
--
Sincerely,
Stephen R. van den Berg.
Auto repair rates: basic labor $40/hour; if you wait, $60; if you watch, $80;
if you ask questions, $100; if you help, $120; if you laugh, $140.
[View Less]
Hi,
I need an example for using the AES encryption in pike 7.4. I can't get
it to work. Thanks a bunch!
--
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
__________________________________________________________
Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor …
[View More]de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail verzoeken wij u dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken.
The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system.
__________________________________________________________
[View Less]