Re: [racket-users] Stack trace

2019-05-02 Thread 'John Clements' via Racket Users
Well, I see two things going on here.

First, this example is an interesting one, because there’s no stack trace to 
display; the (/ 1 n) is the only “frame” left on the “stack”, because the call 
to sub2 has already returned, and the body of “reciprocal” is in tail position 
with respect to the call. If you add a “(+ 1 …)” around the reciprocal call, 
then there’s a stack to display…

…except that you still won’t see an arrow in BSL, because that’s a #lang racket 
thing. That is: if you change the language to “Use language defined in source”, 
and insert #lang racket at the beginning, and add a (+ 1 …) around the 
reciprocal, and run the program, you’ll see an arrow from the (/ 1 n) to the (+ 
1 …) context as I believe you expected.

I think the pedagogically correct answer here is that the arrows that you see 
in racket aren’t really the “right thing” for an educational setting. Instead, 
I think I might suggest using the stepper, instead. (Me? Biased?) In this case, 
I think I would jump to the end of the evaluation, and then step backward to 
see where the error came from.

I also think that there’s probably value in the “tree-cer” approach that 
Krishnamurthi et al. have been working on[*] for Pyret, which shows the 
evaluation of a term as a single large tree, allowing you to inspect each call 
and the arguments that were passed to each call.

John

[*] I thought of it independently, but they thought of it first, and actually 
implemented it. :)


> On May 2, 2019, at 4:02 PM, Mark Engelberg  wrote:
> 
> Working with a student in DrRacket for the first time in a while.
> 
> I notice that in BSL, an error in a function does not tell you what input to 
> the function caused the error, nor does it show the stack trace by drawing 
> arrows in the definitions window the way I remember.
> 
> When did this behavior change? Is there a way to turn on better error 
> reporting and stack traces?
> 
> Example:
> 
> (define (reciprocal n)
>   (/ 1 n))
> 
> (define (sub2 n)
>   (- n 2))
> 
> (define a (reciprocal (sub2 2)))
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to racket-users+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 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[racket-users] Stack trace

2019-05-02 Thread Mark Engelberg
Working with a student in DrRacket for the first time in a while.

I notice that in BSL, an error in a function does not tell you what input
to the function caused the error, nor does it show the stack trace by
drawing arrows in the definitions window the way I remember.

When did this behavior change? Is there a way to turn on better error
reporting and stack traces?

Example:

(define (reciprocal n)
  (/ 1 n))

(define (sub2 n)
  (- n 2))

(define a (reciprocal (sub2 2)))

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[racket-users] PLMW at ICFP: Call for Scholarship Applications (due 17 May)

2019-05-02 Thread David Van Horn
ACM SIGPLAN Programming Languages Mentoring Workshop
Co-located with ICFP'19

PLMW web page: https://icfp19.sigplan.org/home/PLMW-ICFP-2019

The purpose of the programming languages mentoring workshop (PLMW) is to
encourage senior undergraduate and early career (first or second year) to
pursue careers in programming language research. We are specifically
interested in attracting groups who have traditionally not had the
opportunity to participate in research in functional programming. This
workshop will be a combination of learning about the work being done in
several areas of programming language research and mentoring with respect
to helping students prepare for graduate school and the rest of their
career. We will bring together leaders in programming language research
from academia and industry to give talks on the kind of research typically
performed after obtaining a Ph.D. The workshop will engage students,
specifically interested in programming language research, in a process of
imagining how they might contribute to the world.

We especially encourage women and underrepresented minority students to
attend PLMW.

This workshop is part of the activities surrounding ICFP, the International
Conference on Functional Programming, and  takes place the day before the
main conference. One goal of the workshop is to make ICFP conference more
accessible to newcomers. We hope that participants will stay through the
entire conference.

## Travel Scholarship Applications (Due 17 May)

Please fill out this form by 17 May to apply for travel funding.

https://forms.gle/QEvBateG7PRywB336

See the PLMW web page for additional details.

The workshop registration is open to all. Students with alternative sources
of funding are welcome.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[racket-users] Re: Racket News - Issue 7

2019-05-02 Thread Stephen Foster
Yes!  Years ago, "Automata via Macros" was the paper that helped me see 
that macros are cool. :)  Thanks for including that.

I've been enjoying these Racket News issues!

On Wednesday, May 1, 2019 at 7:21:56 AM UTC-7, Paulo Matos wrote:
>
> Issue 7 is here. 
>
> http://racket-news.com/2019/05/racket-news-issue-7.html 
>
> Americano time, enjoy! 
> -- 
> Paulo Matos 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [racket-users] escape ~ in scribble's bib-entry

2019-05-02 Thread stewart mackenzie
$ latex --version
pdfTeX 3.14159265-2.6-1.40.19 (TeX Live 2018/NixOS.org)
kpathsea version 6.3.0
Copyright 2018 Han The Thanh (pdfTeX) et al.
There is NO warranty.  Redistribution of this software is
covered by the terms of both the pdfTeX copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the pdfTeX source.
Primary author of pdfTeX: Han The Thanh (pdfTeX) et al.
Compiled with libpng 1.6.36; using libpng 1.6.36
Compiled with zlib 1.2.11; using zlib 1.2.11
Compiled with poppler version 0.73.0


On Thu, May 2, 2019 at 10:47 PM Matthew Flatt  wrote:
> I'm able to render the document with v7.2. Maybe it depends on the
> Latex installation? I'm using TeXLive 2018 on macOS.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [racket-users] escape ~ in scribble's bib-entry

2019-05-02 Thread Matthew Flatt
At Thu, 2 May 2019 03:33:20 +0800, stewart mackenzie wrote:
> On Thu, 2 May 2019, 03:25 Ben Greenman,  wrote:
> 
> > What version of Racket are you using?
> >
> 
> I'm using v7.2
> 
> The file makes a pdf for me on v7.0
> > (and the current master)

I'm able to render the document with v7.2. Maybe it depends on the
Latex installation? I'm using TeXLive 2018 on macOS.

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.