Re: [Chicken-users] example from rpc egg crashes at around 2k calls for me ....
On Mon, Dec 07, 2015 at 10:38:33PM -0700, Matt Welland wrote: > I don't understand why this is crashing. I'm guessing I'm failing to close > a connection or finalize something. I also saw the same problem when I used > sqlite3 instead of sql-de-lite. Any help or suggestions of where to look > would be appreciated. From the call chain, it looks like something broke during query execution and it's trying to serialize the exception object, which probably contains a reference to the database connection (which is a pointer). Try catching all exceptions and raising a placeholder exception with a simple (error "foo") Cheers, Peter signature.asc Description: Digital signature ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] Why define-constant is not a constant?
I was expecting the identifier 'test1' to not change by using the define-constant form. However i was still able to redefine test1? How to tell the chicken compiler to declare test1 to be a constant for real? CHICKEN (c) 2008-2015, The CHICKEN Team (c) 2000-2007, Felix L. Winkelmann Version 4.10.0 (rev b259631) linux-unix-gnu-x86-64 [ 64bit manyargs dload ptables ] compiled 2015-08-04 on yves.more-magic.net (Linux) #;1> (define-constant test1 "initial value") #;2> (define test1 "I got changed") #;3> test1 "I got changed" #;4> ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Why define-constant is not a constant?
Hi Joe, That's not really what `define-constant` is for. Here, "constant" means "constant value", not "lexical identifier that can't be changed". Even so, the compiler does happen to do what you're expecting (as opposed to the interpreter, where `define-constant` is equivalent to `define`): $ cat foo.scm (define-constant test1 "initial value") (define test1 "I got changed") (print test1) $ csc foo.scm $ ./foo initial value Cheers, Evan ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] ICFP 2016 Call for Papers
[My apologies for the garbled text in a previous version of this email. -- Lindsey] ICFP 2016 The 21st ACM SIGPLAN International Conference on Functional Programming http://conf.researchr.org/home/icfp-2016 Call for Papers Important dates --- Submissions due:Wednesday, March 16 2016, 15:00 (UTC) https://icfp2016.hotcrp.com (in preparation as of December 1) Author response:Monday, 2 May, 2016, 15:00 (UTC) - Thursday, 5 May, 2016, 15:00 (UTC) Notification: Friday, 20 May, 2016 Final copy due: TBA Early registration: TBA Conference: Tuesday, 20 September - Thursday, 22 September, 2016 Scope - ICFP 2016 seeks original papers on the art and science of functional programming. Submissions are invited on all topics from principles to practice, from foundations to features, and from abstraction to application. The scope includes all languages that encourage functional programming, including both purely applicative and imperative languages, as well as languages with objects, concurrency, or parallelism. Topics of interest include (but are not limited to): - Language Design: concurrency, parallelism, and distribution; modules; components and composition; metaprogramming; type systems; interoperability; domain-specific languages; and relations to imperative, object-oriented, or logic programming. - Implementation: abstract machines; virtual machines; interpretation; compilation; compile-time and run-time optimization; garbage collection and memory management; multi-threading; exploiting parallel hardware; interfaces to foreign functions, services, components, or low-level machine resources. - Software-Development Techniques: algorithms and data structures; design patterns; specification; verification; validation; proof assistants; debugging; testing; tracing; profiling. - Foundations: formal semantics; lambda calculus; rewriting; type theory; monads; continuations; control; state; effects; program verification; dependent types. - Analysis and Transformation: control-flow; data-flow; abstract interpretation; partial evaluation; program calculation. - Applications: symbolic computing; formal-methods tools; artificial intelligence; systems programming; distributed-systems and web programming; hardware design; databases; XML processing; scientific and numerical computing; graphical user interfaces; multimedia and 3D graphics programming; scripting; system administration; security. - Education: teaching introductory programming; parallel programming; mathematical proof; algebra. - Functional Pearls: elegant, instructive, and fun essays on functional programming. - Experience Reports: short papers that provide evidence that functional programming really works or describe obstacles that have kept it from working. If you are concerned about the appropriateness of some topic, do not hesitate to contact the program chair. Abbreviated instructions for authors - By Wednesday, March 16 2016, 15:00 (UTC), submit a full paper of at most 12 pages (6 pages for an Experience Report), in standard SIGPLAN conference format, including figures but ***excluding bibliography***. The deadlines will be strictly enforced and papers exceeding the page limits will be summarily rejected. ***ICFP 2016 will employ a lightweight double-blind reviewing process.*** To facilitate this, submitted papers must adhere to two rules: 1. ***author names and institutions must be omitted***, and 2. ***references to authors' own related work should be in the third person*** (e.g., not "We build on our previous work ..." but rather "We build on the work of ..."). The purpose of this process is to help the PC and external reviewers come to an initial judgement about the paper without bias, not to make it impossible for them to discover the authors if they were to try. Nothing should be done in the name of anonymity that weakens the submission or makes the job of reviewing the paper more difficult (e.g., important background references should not be omitted or anonymized). In addition, authors should feel free to disseminate their ideas or draft versions of their paper as they normally would. For instance, authors may post drafts of their papers on the web or give talks on their research ideas. We have put together a document answering frequently asked questions that should address many common concerns: http://conf.researchr.org/track/icfp-2016/icfp-2016-papers#Submission-and-Reviewing-FAQ - Authors have the option to attach supplementary material to a submission, on the understanding that reviewers may choose not to look at it. The material should be uploaded at submission time, as a single pdf or a tarball, not via a URL. This supplementary material
[Chicken-users] optional type checking
Does chicken have optional type checking? A example and pointers to documentation would be nice. Thank you, Jo ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] optional type checking
Joe Python scripsit: > Does chicken have optional type checking? Yes, but only in compiled code. The interpreter ignores all type declarations and makes no type-checks except at run time. > A example and pointers to documentation would be nice. http://wiki.call-cc.org/man/4/Types is the documentation. -- John Cowan http://www.ccil.org/~cowanco...@ccil.org And they pack their lyrics till they're so damn dense You could put 'em in your yard and you could use 'em for a fence. --Alan Chapman, "Everybody Wants to Be Sondheim" ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] example from rpc egg crashes at around 2k calls for me ....
I don't understand why this is crashing. I'm guessing I'm failing to close a connection or finalize something. I also saw the same problem when I used sqlite3 instead of sql-de-lite. Any help or suggestions of where to look would be appreciated. The code (based on the sqlite3 example from the rpc egg): https://www.kiatoa.com/cgi-bin/fossils/megatest/artifact/900250564a62efca I run the server then run four instances of this script: https://www.kiatoa.com/cgi-bin/fossils/megatest/artifact/7217b9abad5d9406 The last output is: [rpc:server] request 2030 from 127.0.0.1; thread2034 (of 0) started... Warning (#): in thread: (serialize) unable to serialize object - can not serialize pointer-like object: # Call history: sql-de-lite.scm:188: ##sys#block-set! sql-de-lite.scm:519: database-error sql-de-lite.scm:856: raise-database-errors sql-de-lite.scm:865: error-message sqlite3-api.scm:35: ##sys#peek-c-string sql-de-lite.scm:864: raise-database-error/status sql-de-lite.scm:871: make-property-condition sql-de-lite.scm:875: make-property-condition sql-de-lite.scm:870: make-composite-condition sql-de-lite.scm:869: abort sql-de-lite.scm:303: finalized? sql-de-lite.scm:304: reset-unconditionally sql-de-lite.scm:188: ##sys#block-set! sql-de-lite.scm:559: set-statement-column-names! sql-de-lite.scm:188: ##sys#block-set! sql-de-lite.scm:295: c1401 <-- ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
