NPE on ((print))
Hi! user= ((print)) NullPointerException user/eval1 (NO_SOURCE_FILE:1) Is that behaviour indended? -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: NPE on ((print))
Hi, Parenthesis are for function invocations in Clojure. ((print)) calls the result of print (which is null) aka. nil, which results in a NPE. Thanks, Ambrose On Thu, Jul 17, 2014 at 1:20 AM, vag.vag...@gmail.com wrote: Hi! user= ((print)) NullPointerException user/eval1 (NO_SOURCE_FILE:1) Is that behaviour indended? -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
NPE in print-stack-trace
I've managed to get an NPE in print-stack-trace: https://gist.github.com/si14/e8d22913d21933d12ef1 It seems highly counter-intuitive to me that this function can throw NPEs. I thought it's intended to be used in catch clauses; does it mean that I should wrap some catches in their own try-catches? Anderkent in #clojure suggested that the cause of this NPE is an exception without stacktrace, similar to ones discussed here: http://jawspeak.com/2010/05/26/hotspot-caused-exceptions-to-lose-their-stack-traces-in-production-and-the-fix/ If this is the case, the situation is even worse, because it's hard to foresee this optimization. -- -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: NPE in print-stack-trace
You might be hitting a bug in Clojure 1.5.1 where it incorrectly attempts to access elements in an empty stack trace, which I have seen occur. This should be fixed in Clojure 1.6.0 alpha releases: http://dev.clojure.org/jira/browse/CLJ-1102 Andy On Tue, Dec 17, 2013 at 9:14 AM, Dmitry Groshev lambdadmi...@gmail.comwrote: I've managed to get an NPE in print-stack-trace: https://gist.github.com/si14/e8d22913d21933d12ef1 It seems highly counter-intuitive to me that this function can throw NPEs. I thought it's intended to be used in catch clauses; does it mean that I should wrap some catches in their own try-catches? Anderkent in #clojure suggested that the cause of this NPE is an exception without stacktrace, similar to ones discussed here: http://jawspeak.com/2010/05/26/hotspot-caused-exceptions-to-lose-their-stack-traces-in-production-and-the-fix/ If this is the case, the situation is even worse, because it's hard to foresee this optimization. -- -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Clojure group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups Clojure group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
