Pike-devel

pike-devel@lists.lysator.liu.se

3046 discussions

Compiling programs in Pike master with proper error messages
by Stephen R. van den Berg 07 Jun '20

07 Jun '20

I'm using the following function in my spike-webserver: object compileit(string file, void|int quiet) { object prog; if (!quiet) log("Compiling %s", file); if (mixed err = catch(prog = compile_file(file)())) log(LOG_ERR, "Compile error %s", describe_backtrace(err)); return prog; } in order to compile modules. I'd like two things though, which currently don't quite work as I had hoped: a. When there is a compilation problem, I get a backtrace here, but it does not reveal what compilation error occurred (it does not show line number and diagnostics). Any suggestions how to get those? b. I'd like a (list of) custom library directories which I want to include in the namespace, without having to specify them on the commandline using -L options. How can this be accomplished? -- Stephen.

3 2

Protocols.HTTP.params_encode() and _decode()
by Stephen R. van den Berg 30 May '20

30 May '20

After having needed to program (HTTP) parameter decoding/encoding for the nth time, I decided to add some proper code for generic use. Any objections to the interface and/or naming? Is the solution fast enough? -- Stephen.

2 7

Annotation question
by H William Welliver 28 May '20

28 May '20

Given: A.pmod/B.pike inherit Pike.Annotation; A.pmod/C.pike inherit Pike.Annotation; and test.pike: @A.B; @A.C: string foo; function bar; class gazonk { @A.B; } I can do: > object o = ((program)"test.pike")(); > mkmapping(indices(o), annotations(o)); (1) Result: ([ /* 3 elements */ "bar": 0, "foo": (< /* 1 element */ A.C >), "gazonk": 0 ]) But I’m puzzled as to why gazonk is 0 and not (<A.B>). Also, how would I query program(“test.pike”) to see that it has A.C defined within it? I have not dug too far into this yet, just hoping there’s an obvious answer I’ve missed. Thanks in advance! Bill

1 0

Re: GL build error on MacOS 10.14
by Marc Simpson 28 May '20

28 May '20

On Thu, May 28, 2020 at 8:48 AM Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > > >Also, GL is deprecated as of 10.14, > > Hm? They can't seriously expect people to use Vulcan or some crap > like that, can they? "Metal", apparently: https://appleinsider.com/articles/18/06/28/why-macos-mojave-requires-metal-…

1 0

GL build error on MacOS 10.14
by H William Welliver 28 May '20

28 May '20

[I’m not very familiar with this module, so I’ll leave this as a bug report rather than fixing it myself] On MacOS 10.14, master fails to build the GL module with the following error: /Users/hww3/devel/pike/src/post_modules/GL/GLSL.cmod:800:5: error: use of undeclared identifier 'GL_LUMINANCE8_EXT Thats in glext.h but is guarded by GL_EXT_texture, so defining that before the include seems to make the error go away. Also, GL is deprecated as of 10.14, so in order to cut down on noise, I added -DGL_SILENCE_DEPRECATION to my build. Not sure if that’s desirable in general. Also, I noticed a bunch of grumbling in the Kerberos and GSSAPI modules about deprecations. Think that’s harmless noise (for now). Bill

2 1

Protocols.HTTP.Server.Request and a reference back to the listening socket?
by Stephen R. van den Berg 28 May '20

28 May '20

Once you have an accepted connection in Protocols.HTTP.Server.Request, is there a reference to the original listening socket the connection was accepted on? Why don't we preset the set_id()/query_id() value on the accepted socket with the one from the listening socket? -- Stephen.

1 1

Re: RFC: Attributes in Markdown text
by Chris Angelico 22 May '20

22 May '20

On Fri, May 22, 2020 at 9:28 AM Martin Nilsson (Coppermist) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > > > > >How does that sound? > > > > Sounds good to me. The expectations should be to move it from Tools to > Parser (or something) also once the changes are done. Cool. The changes are done, including that move - which actually is a move *back*. For compatibility reasons, I've kept a little shim in Tools, so you can still call Tools.Markdown.parse() as before. At the moment, it's on branch rosuav/markdown-parser-extensibility but I'm fairly sure there won't be any backward compatibility problems. If anyone else can test any of their Markdown code, I'd appreciate it, just as a quick check. If no objections and no issues found, I'll merge it into master some time next week. ChrisA

1 0

Re: RFC: Attributes in Markdown text
by Chris Angelico 21 May '20

21 May '20

On Fri, May 22, 2020 at 4:00 AM Martin Nilsson (Coppermist) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > > While I'm indifferent to markdown itself, my problem with the markdown > implementation in Pike is that it was implemented as an application > with no programmatic way of controlling its behavior. That's why we > moved it into the Tools module. A proper markdown module should be > easy to extened and control from code. Okay. Here's a proposal then. I'll go through the Markdown module and give it a bunch of hooks intended for subclasses, and also unprotect Parser and Lexer. Then anyone can do something like: class Renderer { inherit Tools.Markdown.Renderer; string table(string header, string body, mapping attrs) { return ::table(header, body, attrs | (["border": "1"])); } } as an easy way to make a small tweak to the behaviour. And yes, part of this would be that every HTML tag emitter would take an attrs mapping, which would then mean that my original proposal (having a specially-formatted block at the end of a paragraph) would become a simple job of subclassing the parser. (Oh, and I'd add a Parser entry to the options mapping, to make it easier and more logical to override. Same as Renderer currently is.) How does that sound? ChrisA

2 1

RFC: Attributes in Markdown text
by Chris Angelico 21 May '20

21 May '20

See branch: rosuav/markdown-attribute-syntax There's a not-very-well-known syntax supported by some Markdown parsers (including GitHub Flavored Markdown) that allows HTML attributes to be attached to a paragraph of text: Text goes here blah blah blah {: someattr=value otherattr=otherval} This is extremely handy for making small adjustments to the display of something, particularly with shorthands for class and ID, for use in CSS: {: .someclass} {: #someid} However, it's not well documented and I can't find a standard anywhere for it. It is something that I personally would find extremely useful, and am currently implementing by subclassing the Markdown module and tweaking the parser. Would anyone else find this of value? Conversely, would anyone find that this causes issues? ChrisA

3 4

Build failure on macOS (HEAD of master)
by Marc Simpson 01 May '20

01 May '20

Hi all, FYI, it looks like master no longer builds on macOS due to the MTU additions in [44f12ac]: .../src/modules/_Stdio/file.c:5526:16: error: use of undeclared identifier 'IP_MTU' int option = IP_MTU; .../src/modules/_Stdio/file.c:5541:14: error: use of undeclared identifier 'IPV6_MTU' option = IPV6_MTU; Best, Marc

1 1

Jump to page:

2026

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