Pike-devel August 2014

pike-devel@lists.lysator.liu.se

9 participants
28 discussions

Branches for discussion: Pango.Layout xy_to_char, Stdio.File nodelay
by Chris Angelico 28 Aug '14

28 Aug '14

Both of these have been discussed previously, but now they're posted as topic branches in the main repo. (I've also pushed a few non-controversial GTK2 changes to the 8.0 and 7.8 branches.) Branch: rosuav/pango_xy_to_char Adds a new method xy_to_char() to the GTK2.Pango.Layout object, parallel to xy_to_index(). It'll be slower, as it has to do more work, but it feels cleaner. Pike code constructs Pango layout objects using Unicode strings, not UTF-8, so getting back character indexes makes more sense than byte positions. Branch: rosuav/naglingcontrol Adds a new method nodelay() to Stdio.File to control the TCP_NODELAY flag. This is definitely debatable, as there's now starting to be more of a proliferation of flag-controlling methods. Would it be better to have a single method to set/reset flags? How should detection of available flags be done? (With the nodelay() method, the presence of the function implies its callability.) If this were Python, we'd have a lengthy python-ideas thread and probably a PEP to discuss this. :) Thoughts? ChrisA

2 2

Sql.pgsql behavior in case of errors
by aldem-pikedev＠aldem.net 21 Aug '14

21 Aug '14

Hi everyone, I am preparing to use Postgres in my app, found the following strange behavior: ---snip--- Sql.Sql db = Sql.Sql("pgsql://localhost", "test", "test", "test"); db->query("BEGIN"); db->query("INSERT INTO requests (SvTrId) VALUES ('lala')"); catch(db->query("INSERT INTO requests (SvTrId) VALUES ('lala')")); db->query("INSERT INTO requests (SvTrId) VALUES ('juju')"); db->query("ROLLBACK"); ---snip--- Database is opened, row with 'lala' is inserted, second query (obviously) fails as SvTrId is the primary key, but row with 'juju' is inserted *and* appears in the database - i.e. the transaction is *committed*! Studying source code show, that once error is encounter, session is reset, i.e. running transaction is rolled back, everything is closed, temporary tables are deleted and session variables are reset as well, and after that, the next statement(s) will be committed immediately, as there is no active transaction. In my opinion, this is not exactly correct behavior when statement fails, as session still may be needed (especially temporary tables, open cursors etc). Im some cases, this is perfectly normal when SQL statement fails, especially in SERIALIZED transaction isolation level, and it would be more practical to leave the decision as of what to do to the application. Yes, this is true that it is impossible to continue executing statements in failed transaction, but temporary tables etc. may still be needed. Also, silent reconnection is not a good idea too - when there are many transactional statements are executed - it would be nice to have an option to modify this behavior. Best regards, /Alexander

5 6

Re: zero_type of implicit return
by Chris Angelico 18 Aug '14

18 Aug '14

On Mon, Aug 18, 2014 at 7:15 AM, Mirar @ Pike developers forum <10353(a)lyskom.lysator.liu.se> wrote: > I can't imagine any code that relies on that a function not returning > anything is returning 0 and not UNDEFINED. Hmm. Actually, I think you're right. I do frequently make use of the implicit zero return, but never checking its zero_type. ChrisA

1 0

Re: zero_type of implicit return
by Chris Angelico 17 Aug '14

17 Aug '14

On Sun, Aug 17, 2014 at 3:15 AM, Martin Nilsson (Opera Mini - AFK!) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > Would it make sense if the implicit return 0; in pike functions > had a different zero type than 0, like UNDEFINED? I'm conceptually okay with it, but it will break code. ChrisA

3 2

zero_type of implicit return
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 16 Aug '14

16 Aug '14

Would it make sense if the implicit return 0; in pike functions had a different zero type than 0, like UNDEFINED?

2 1

Re: Development discussion
by Peter Bortas 15 Aug '14

15 Aug '14

On Thu, Aug 14, 2014 at 4:30 PM, Per Hedbor () @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: >> ** remove class equals (too many equals) > > This somewhat obscure point is probably the existence of a whole bunch > of x [op]= op-codes (+=, -=, &=, %= etc) You brought it up, so however you define it is the correct definition. -- Peter Bortas

3 2

Re: Hilfe-crash.
by Chris Angelico 11 Aug '14

11 Aug '14

On Mon, Aug 11, 2014 at 4:20 AM, Martin Nilsson (Opera Mini - AFK!) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > After the new code generation I get a consistent crash if I start > hilfe and does arrow up. Not very helpful backtrace though. It seems to depend on having a good-sized .hilfe_history. I was unable to reproduce the crash with no history, or with just a couple of lines. The crash happens as you describe if there are at least 9 lines in history; if there are exactly 8, then pressing up won't crash, but pressing down afterward will. Don't know if that helps at all or not. ChrisA

3 4

Hilfe-crash.
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 11 Aug '14

11 Aug '14

After the new code generation I get a consistent crash if I start hilfe and does arrow up. Not very helpful backtrace though. Pike v8.0 release 3 running Hilfe v3.5 (Incremental Pike Frontend) > Program received signal SIGSEGV, Segmentation fault. 0x00002aaaacd583d8 in ?? () (gdb) bt #0 0x00002aaaacd583d8 in ?? () #1 0x0000000000000027 in ?? () #2 0x00000000008902e0 in ?? () #3 0x00002aaaacd986b1 in ?? () #4 0x00002aaaac12d1b0 in ?? () #5 0x0000000000886338 in ?? () #6 0x00000000008902e0 in ?? () #7 0x000000000095c080 in ?? () #8 0x000000000041e060 in eval_instruction ( pc=0x2aaaacd986b1 "UH\211\345AWAVAUATSH\203\354\bI\211\377M\213w H\215\005\365\377\377\377I\211F(M\213/I\213N8H\213\001H\213I\bI\211E") at /home/nilsson/pike/src/interpret.c:1707 #9 catching_eval_instruction ( pc=0x2aaaacd986b1 "UH\211\345AWAVAUATSH\203\354\bI\211\377M\213w H\215\005\365\377\377\377I\211F(M\213/I\213N8H\213\001H\213I\bI\211E") at /home/nilsson/pike/src/interpret.c:2749 #10 0x000000000041f3b0 in inter_return_opcode_F_CATCH ( addr=0x2aaaac2b4000 "@\323\022\254\252*") at /home/nilsson/pike/src/interpret.c:1291 #11 0x00002aaaacd98699 in ?? () #12 0x0000000000034cf0 in ?? () #13 0x00000000008902e0 in ?? () #14 0x0000000000000000 in ?? ()

2 1

Re: Codepage decoding tables have incorrect data
by Chris Angelico 07 Aug '14

07 Aug '14

On Tue, Aug 5, 2014 at 6:55 AM, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > And I'd be inclined to fix any acctual errors, rather than blindly > following one or the other. :-) > > Just so you know, the MAPPINGS files on unicode.org is not part of > the Unicode standard, so they are no more a standard than RFC 1345 is. Oh! Okay. What is the standard? Where would I find an authoritative set of codepage-to-Unicode character set replacements? All I can confirm is that, with the changes I put through, Pike agrees with Python 3.4, and codepage 437 "looks right", neither of which is anything official. ChrisA

3 4

Re: Codepage decoding tables have incorrect data
by Chris Angelico 07 Aug '14

07 Aug '14

On Fri, Aug 8, 2014 at 1:50 AM, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > Ok. Then my approach would be to keep things as they are until > someone comes up with a specific complaint. :-) As I said, the box > drawing stuff is fixed, so feel free to raise a new issue if you find > something else which is a concrete problem. Yeah, I agree. Codepages are a mess anyway; as long as there's some kind of reasonably sane translation done, it's as good as it's going to be. > (As a side note, I think you were justified in assuming thick/double > lines was a font issue. There is no semantical difference, so I > imagine the only reason why Unicode assigns separate codepoints to > them instead of treating them as font variants is for compatibility > with some other encoding that has both...) No idea. To be quite honest, I wasn't even aware of those other box-drawing characters' existence until I came across this... there's so much Unicode that it's impossible to see it all. ChrisA

1 0

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 August 2014