Re: Adding to the end of the load path

2012-11-15 Thread Noah Lavine
Hello, This is coming late in the discussion, but I'd like to suggest a somewhat different approach. I hope this is helpful. It seems to me that in the end, the module-lookup system may need to be more complex than having regular and suffix lookup paths. For instance, one of the big concerns here

Re: Adding to the end of the load path

2012-11-15 Thread Ludovic Courtès
Mark H Weaver skribis: >> However, I can live with that, but maybe we can have it both >> ways: >> >> - Add the _SUFFIX environment variables, making it clear in the docs >> that they are supported only from Guile 2.0.7 onward. > > Yes, I agree this is a good idea. But then, what would happen

Re: thoughts on native code

2012-11-15 Thread Andreas Rottmann
Sjoerd van Leent Privé writes: > Hi Stefan, > > Just my idea about an assembler in Scheme. Sounds interesting. If it's > done properly, it can be very promising to use scheme itself to > directly emit machine instructions. This would also be interesting for > meta compilation in the future (think

Re: Adding to the end of the load path

2012-11-15 Thread Mark H Weaver
Hi Andreas, Andreas Rottmann writes: > l...@gnu.org (Ludovic Courtès) writes: > >> I pretty much like Mark’s suggestion of using ‘...’ as a special marker, >> even though that’s a valid file name. >> > Well, there's a workaround -- specifying "./..." as an "escape sequence" > for "..." if you re

Re: Adding to the end of the load path

2012-11-15 Thread Ludovic Courtès
Hi Andreas, Andreas Rottmann skribis: > l...@gnu.org (Ludovic Courtès) writes: [...] >> I pretty much like Mark’s suggestion of using ‘...’ as a special marker, >> even though that’s a valid file name. >> > Well, there's a workaround -- specifying "./..." as an "escape sequence" > for "..." if

Re: Adding to the end of the load path

2012-11-15 Thread Andreas Rottmann
l...@gnu.org (Ludovic Courtès) writes: > Hi! > > Sorry for the delay. > > Andreas Rottmann skribis: > >> Ian Price writes: > > [...] > >>> Andreas Rottmann suggested something similar in February[1]. >>> >> I've attached a patch implementing that suggestion, FWIW. >> >>> I don't have any concret

Re: thoughts on native code

2012-11-15 Thread Ludovic Courtès
Hello, Regarding the assembler, if I were to actually hack something ;-), I’d choose Sassy [0], along with Industria’s disassemblers [1]. Ludo’. [0] http://sassy.sourceforge.net/ [1] http://weinholt.se/industria/

Re: thoughts on native code

2012-11-15 Thread Stefan Israelsson Tampe
Hi, Yes this is pre-work and what i'm doing is an investigation trying out things. bare that in mind :-) For the assembler it can be really good to support one that comes with guile so I do not find this work as a research work but as a service work to propose components that can be included in g

Re: thoughts on native code

2012-11-15 Thread Mark H Weaver
Before anyone spends any more time on this, I want to make it clear that although I very much appreciate Stefan's pioneering spirit, and some of his ideas are likely to be incorporated, Stefan's work on native compilation is an independent project of his, and is unlikely to be merged into the offic

Re: thoughts on native code

2012-11-15 Thread Stefan Israelsson Tampe
Arg, I prematurely send that mail, well here is the continuation 4. I prefere to have an evironment like (assemble target (inst jmp label:) (inst mov b a) label: (inst mov b c) This makes the labels stand out and makes for a nice read of the assembler. You can see how we

Re: thoughts on native code

2012-11-15 Thread Stefan Israelsson Tampe
Hi Sjoerd, 1. I (mov dst src), this is what's used in the rtl vm code in C and I would like to keep a match between the two 2. I wouldl like to have prefix for instruction to mark those out like (inst mov dst src) 3. It would be nice to have a default size of the architecture e.g. (inst

Re: thoughts on native code

2012-11-15 Thread Sjoerd van Leent Privé
Hi Stefan, Just my idea about an assembler in Scheme. Sounds interesting. If it's done properly, it can be very promising to use scheme itself to directly emit machine instructions. This would also be interesting for meta compilation in the future (think of aiding GCC). So you are thinking a