Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

Re: pike.lysator access
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 03 Jan '14

03 Jan '14

> Hi Grubba, Hi Bill. > Thanks for looking into this for me. I just tried to log in to > pike.lysator.liu.se and was prompted for a password. I did verify > that both ida and git accounts work properly with the keys I'm > using. Can you take a look to make sure things are okay? After some investigation, I found that the problem was that sshd didn't like the password entry for your account. Try now. > Bill /Grubba

1 0

pike.lysator access
by H. William Welliver III 02 Jan '14

02 Jan '14

I've got a pike 7.8 alpha prepared, but I'm having trouble logging in to pike.lysator.liu.se. Can someone with access verify my account (bill) and key? I'm still able to access the server at liu, so if that key can be used, that'd be helpful. Bill

2 1

pre files for gtk
by Per Hedbor () ＠ Pike (-) developers forum 09 Dec '13

09 Dec '13

> I was looking at the GTK support in Pike and noticed the wrappers > where some sort of pre-files in src/post_modules/GTKx > > So are these just a special case of mods that new_build_pgtk.pike > generates and not another supported way of writing cmods? These are rather special, and are only handled by the above mentioned build_pgtk.pike It is called from the build-step (from the Makefile), and the output is C-files, not .cmod-files. .cmod did not really exist as such when the module was first written, also it capitalizes on the fact that the GTK API is rather predictable and easy to generate code for, most of the time the function prototypes are more than enough. The output ends up in build/<OS-name>/post_modules/pgtk*.c There is also a wrapper for the glib-introspection API written by Marcus Comstedt that he showed off a year or so ago, I think it was on a branch in git? Anyway, that one can fairly easily be used to use the gtkwebkit widget directly.

4 4

Stack
by Stephen R. van den Berg 05 Dec '13

05 Dec '13

Did someone try this on the Pike codebase already? http://css.csail.mit.edu/stack/ -- Stephen. "As of Postgres v6.2, time travel is no longer supported." -- PostgreSQL Manual

2 1

7.8 Changelog
by H. William Welliver III 04 Dec '13

04 Dec '13

I've just committed a first attempt at a change log for the next 7.8 release. Please take a look and make or suggest any changes you feel appropriate. I'd like to cut an alpha release some time in the next week. Bill

1 0

Cryptography update
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 22 Nov '13

22 Nov '13

A small progress report update on the cryptographic developments. It is now possible to generate and validate certificates signed with DSA SHA1/SHA224/SHA256 and RSA MD2/MD5/SHA1/SHA256/SHA384/SHA512. I've successfully verified openssl certificates with the X509 module, and as a system test I've set up a TLS webserver with DSA certificate and had wget (using openssl) download from it. Besides the key generation, I feel that this part of the code is now in good shape.

1 0

Top links in documentation looks broken
by Tor Edvardsson ＠ Pike developers forum 18 Nov '13

18 Nov '13

The top liknks in the documentation looks really broken. The links have line breaks so its just messed thinks up. Best would be to scrap the table layout and just have a ul-list for it.

1 0

Re: Pike 8 @ Pike conf 2013
by Chris Angelico 17 Nov '13

17 Nov '13

On Mon, Nov 18, 2013 at 12:25 AM, Henrik Grubbström (Lysator) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: >>On Sun, Nov 17, 2013 at 11:40 PM, Henrik Grubbström (Lysator) @ Pike >>(-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: >>>>This looks like a good opportunity to mention a few patches that I >>>>haven't heard back regarding. They're mostly fairly trivial/simple. Is >>>>there a better way to suggest patches than posting them to this list >>>>or pike@roxen? >>> >>> Either works. >>> >>> Applied all of them except for the low_read_file() patch, >>> which I fail to see a reason for. >> >>Thanks! >> >>That was to cure a compiler warning using gcc on OS/2, if I recall >>correctly. Not a big deal, was just a "try to make sure things are >>safe" check. Unlikely - if even possible - to make a difference on any >>actually-supported platform. > > The PRINTPIKEOFFT stuff is intended to fix such warnings. A problem > with the patch was that it wasn't 64-bit clean, and as it is just a > fatal diagnostic I don't see any reason to change it. Fair enough! I'll discard the patch. Woot! That means I'm now running a clean 8.0! ChrisA

1 0

Re: Pike 8 @ Pike conf 2013
by Chris Angelico 17 Nov '13

17 Nov '13

On Sun, Nov 17, 2013 at 11:40 PM, Henrik Grubbström (Lysator) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: >>This looks like a good opportunity to mention a few patches that I >>haven't heard back regarding. They're mostly fairly trivial/simple. Is >>there a better way to suggest patches than posting them to this list >>or pike@roxen? > > Either works. > > Applied all of them except for the low_read_file() patch, > which I fail to see a reason for. Thanks! That was to cure a compiler warning using gcc on OS/2, if I recall correctly. Not a big deal, was just a "try to make sure things are safe" check. Unlikely - if even possible - to make a difference on any actually-supported platform. ChrisA

2 1

Re: Pike 8 @ Pike conf 2013
by Chris Angelico 17 Nov '13

17 Nov '13

On Sun, Nov 17, 2013 at 2:15 AM, Henrik Grubbström (Lysator) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > And now the branch and Pike 8.0.1 exist: > > | Pike v8.0 release 1 running Hilfe v3.5 (Incremental Pike Frontend) > | > Cool! This looks like a good opportunity to mention a few patches that I haven't heard back regarding. They're mostly fairly trivial/simple. Is there a better way to suggest patches than posting them to this list or pike@roxen? ChrisA

2 1

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