Pike-devel June 2012

pike-devel@lists.lysator.liu.se

7 participants
14 discussions

debugger opcodes
by Bill Welliver 30 Oct '14

30 Oct '14

I noticed that folks have been working on code generation lately. Any chance it might be possible to implement some of the opcodes required to get debugging working (step, break, etc)? I seem to recall someone indicating it wasn't a terribly difficult task, but it's clearly beyond my understanding of the problem. Bill

4 6

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

Final feedback for 7.8.686
by H. William Welliver III 29 Jun '12

29 Jun '12

It's been about 2 weeks since I cut a new 7.8 release candidate and I haven't heard much feedback, good or bad. Since there weren't many problems with the previous release, I'm going to assume that everything is okay. However, if anyone has any feedback, please let me know, as I plan to mark it as an "official release" build. Assuming all goes well, what are the changes that a Windows build and friends can be ready in the near future? I tried doing a build, but I think things have moved on (at the time, using VC6 worked, etc) since my last Windows build adventure. Best, Bill

4 3

ZIP file program loader
by Bill Welliver 21 Jun '12

21 Jun '12

When I was in Sweden last fall, I remember having a brief conversation with someone who'd written a resolver that loads classes or modules from a tar or zip file (the details are a little hazy). Does that sound familiar to anyone here? If so, do you have any code you might be willing to share? Bill

4 7

USB.devices OneWire.devices, how to unite it into an IO module?
by Stephen R. van den Berg 14 Jun '12

14 Jun '12

I currently have a functioning usblib module, and for now it lives in src/post_modules/USB in my personal tree. I am now embarking onto creating a OneWire module/class which uses the aforementioned USB lib to actually communicate with the 1-wire busmaster. The question is, where do I put all these modules. Most logical would be under a module named IO, so it would become IO.USB.devices and IO.OneWire.devices or somesuch. Then again, the USB module is completely written as a cmod. The OneWire module might live as a Pike module. How do I solve the namespace problem, I'd like to unite them under master module IO? Renaming the USB module to _USB, then inheriting the module under lib/modules/IO.pmod again might work, but gets messy with autodoc, since I'd like to keep the documentation in the cmod file itself. Any suggestions? -- Stephen. How many weeks are there in a lightyear?

8 32

New Pike Beta: 7.8.686
by H. William Welliver III 13 Jun '12

13 Jun '12

I've made a new beta build which for your consideration. If no problems are found, this build will become the next stable release. Please download, build, test, make binary packages, etc. As always, please report back with any problems (or successes, too!) http://pike.ida.liu.se/download/pub/pike/beta/7.8.686/ Best, Bill

1 0

Pike 7.8 Release (last call)
by H. William Welliver III 13 Jun '12

13 Jun '12

Does anyone have any objections to 7.8.680 becoming the next official release of Pike? Do note that machine code is non-functional on (at least more modern instances of) i386. If I don't hear any objections in 24 hours, I will attempt to update the website, etc, with the new information. Best, Bill

9 18

Starting with USB() instead of USB.devices()
by Stephen R. van den Berg 10 Jun '12

10 Jun '12

I now have a cmod which is in a subdir src/post_modules/USB, which gives me an USB.devices(), USB.Iterator(), USB.device() and USB.transfer(). The usual way this works, is that one starts with: object dev=USB.devices(); and then you do a foreach() which gets the Iterator, which delivers the devices, etc. Now, what if I'd like it to start with: object dev=USB(); (and then the rest with foreach() etc. same as above). Are there any aesthetical or technical reasons not to prefer this? (I'm all for brevity). If there are no obvious objections, what would be the easiest way to implement this? Is this doable in the cmod? Are there any existing modules that did it this way? -- Stephen. "There are three types of people in this world: those who make things happen, those who watch things happen and those who wonder what happened."

2 4

PIKEVAR object foo;
by Stephen R. van den Berg 09 Jun '12

09 Jun '12

If I declare this inside a PIKECLASS in a .cmod, I need the canonical: PIKEFUN void setfoo(void|object foo) { if(THIS->foo) free_object(THIS->foo); if((THIS->foo=foo)) { debug_malloc_touch(THIS->foo); Pike_sp--; /* don't decrease references */ } else pop_stack(); } to set it. The question is, should I also free_object() it in the destructor, or does Pike already take care of that somewhere? -- Stephen. How many weeks are there in a lightyear?

4 10

quick_add_*_constant() not so quick
by Stephen R. van den Berg 05 Jun '12

05 Jun '12

Is there a reason why quick_add_integer_constant takes a char* and a length, instead of a (much quicker and cleaner) struct pike_string* which would enable it to work more efficiently in collaboration with MK_STRING() ? I see that the functions do not seem to be used anywhere, so I propose to change the (internal) interface definition for them to actually make them quick. -- Stephen. "There are 10 types of people in the world. Those who understand binary and those who do not."

3 5

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 June 2012