>From what I understand, the reader will call the tag function, thus being 
executed at read time and not compile time.

On Thursday, March 7, 2013 4:04:15 AM UTC-5, Akhil Wali wrote:
>
> IMHO features expressions should be evaluated at read-time only.
> Putting it off till the compilation phase only complicates things.
> So I'm actually favoring a preprocessing step like here -  
> http://dev.clojure.org/display/design/Feature+Expressions?focusedCommentId=6390066#comment-6390066
>
> The idea is simple; when the reader parses a sexpr, and if there's a 
> feature expression,then  only use the part that's relevant to the current 
> Clojure dialect.
> The only complication with this scheme is that all information in 
> *clojure-version* is related to the version numbers only; however, this 
> could be changed easily.
>
>
>
> On Thu, Mar 7, 2013 at 7:46 AM, Brent Millare 
> <brent....@gmail.com<javascript:>
> > wrote:
>
>> +1
>>
>> Isn't is possible to accomplish all these efforts using tagged literals? 
>> https://github.com/miner/wilkins
>>
>> This way the facilities for read-time code generation can be customized 
>> and any reader that supports tagged-literals will support this. All of this 
>> is data provided as arguments, no evaluation. Evaluation happens from the 
>> tag function.
>>
>> On Wednesday, March 6, 2013 8:24:15 PM UTC-5, Brian Goslinga wrote:
>>>
>>> Do we really need new syntax for feature expressions? Although it would 
>>> be more ugly than CL's feature expressions, we could use a reader literal. 
>>> For example #feature [<feature expression> <value>]. Using a reader literal 
>>> is simple, compatible with EDN, and allows for the feature expressions to 
>>> be backported to an older version of Clojure using a library.
>>
>>  -- 
>> -- 
>> You received this message because you are subscribed to the Google
>> Groups "Clojure" group.
>> To post to this group, send email to clo...@googlegroups.com<javascript:>
>> Note that posts from new members are moderated - please be patient with 
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+u...@googlegroups.com <javascript:>
>> 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+u...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>
>
> -- 
> Akhil Wali 
>
> # http://github.com/darth10 <https://github.com/darth10>
> # http://darth10.github.com
>
>  

-- 
-- 
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.


Reply via email to