Re: [pollen] Splitting multiple-output tag functions with a Racket macro

2016-11-14 Thread Matthew Butterick
On Nov 14, 2016, at 1:49 PM, Joel Dueck wrote: > > When you talk about functions transparently overriding other functions in > some kind of inheritance hierarchy, are you talking about ... classes? > > http://docs.racket-lang.org/guide/classes.html > > I'm familiar with inheritance and overlo

Re: [pollen] Splitting multiple-output tag functions with a Racket macro

2016-11-14 Thread Joel Dueck
On Monday, November 14, 2016 at 1:48:39 PM UTC-6, Matthew Butterick wrote: > > > When you talk about functions transparently overriding other functions in > some kind of inheritance hierarchy, are you talking about ... classes? > > http://docs.racket-lang.org/guide/classes.html > I'm familiar wit

Re: [pollen] Splitting multiple-output tag functions with a Racket macro

2016-11-14 Thread Matthew Butterick
On Nov 14, 2016, at 10:40 AM, Joel Dueck wrote: > What if Pollen automatically branched to tag functions prefixed with pdf: > when current-poly-target is 'pdf ? That is, if 'pdf is the current target, > Pollen would check for pdf:strong and, if it didn't find one, default to > plain-ol strong

Re: [pollen] Splitting multiple-output tag functions with a Racket macro

2016-11-14 Thread Joel Dueck
> > I like these ideas, and it suggests to me that Pollen could have some > better tools built in for managing poly projects. > I agree, any additional facilities for splitting out the logic of tag functions by output format would be welcome as long as they aren't too complicated. After try