﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>pb commented on Boo Imports &amp; New Usages</title><description>This has something similar, I actually use this for deployment with some additions that make it work like running a .bat file
  
  
http://www.members.optusnet.com.au/~olegshilo/
</description><link>http://ayende.com/2857/boo-imports-new-usages#comment7</link><guid>http://ayende.com/2857/boo-imports-new-usages#comment7</guid><pubDate>Fri, 12 Oct 2007 11:24:29 GMT</pubDate></item><item><title>Ayende Rahien commented on Boo Imports &amp; New Usages</title><description>Avish,
  
Because then I get into the usual pre-processor errors. In other words, the code that I write and the code that the compiler sees are two different steps.
  
  
It also means that I now need to think about the file structure.
  
  
Imagine:
  
  
"file_to_include.boo"
  
  
import X
  
import Y
  
  
  
someVar = 0
  
  
  
"including_file.boo"
  
  
#include file_to_include.boo
  
  
import Z
  
  
print "Hi"
  
  
Using a preprocessor will produce uncompilable code.
  
</description><link>http://ayende.com/2857/boo-imports-new-usages#comment6</link><guid>http://ayende.com/2857/boo-imports-new-usages#comment6</guid><pubDate>Fri, 12 Oct 2007 10:57:53 GMT</pubDate></item><item><title>Avish commented on Boo Imports &amp; New Usages</title><description>My point is that you don't need knowledge of the AST. Why write a "load that file, look for import statements and copy them here" when all you need is "load that file and copy it here"? 
</description><link>http://ayende.com/2857/boo-imports-new-usages#comment5</link><guid>http://ayende.com/2857/boo-imports-new-usages#comment5</guid><pubDate>Fri, 12 Oct 2007 10:29:29 GMT</pubDate></item><item><title>Ayende Rahien commented on Boo Imports &amp; New Usages</title><description>Also, overkill?
  
That is about 30 lines of code.
</description><link>http://ayende.com/2857/boo-imports-new-usages#comment4</link><guid>http://ayende.com/2857/boo-imports-new-usages#comment4</guid><pubDate>Thu, 11 Oct 2007 13:43:27 GMT</pubDate></item><item><title>Ayende Rahien commented on Boo Imports &amp; New Usages</title><description>I wouldn't call it preprocessor, not when it is has knowledge of the language AST.
</description><link>http://ayende.com/2857/boo-imports-new-usages#comment3</link><guid>http://ayende.com/2857/boo-imports-new-usages#comment3</guid><pubDate>Thu, 11 Oct 2007 13:43:19 GMT</pubDate></item><item><title>Avish commented on Boo Imports &amp; New Usages</title><description>I agree, this sounds interesting. The WS example in particular. However, the last example looks more like an #include to me. Boo needs a preprocessor, and writing a compiler step that just copies imports from one file to another is very specialized overkill, when all you need is a preprocessor supporting #include and #define. 
</description><link>http://ayende.com/2857/boo-imports-new-usages#comment2</link><guid>http://ayende.com/2857/boo-imports-new-usages#comment2</guid><pubDate>Thu, 11 Oct 2007 13:37:33 GMT</pubDate></item><item><title>Shane Courtrille commented on Boo Imports &amp; New Usages</title><description>This definitely sounds interesting....
</description><link>http://ayende.com/2857/boo-imports-new-usages#comment1</link><guid>http://ayende.com/2857/boo-imports-new-usages#comment1</guid><pubDate>Wed, 10 Oct 2007 22:58:41 GMT</pubDate></item></channel></rss>