D front-end in D for D

I just got an amazing thought. If we end up getting a D front-end in D, I think it would be possible to make the back-end in the same space as the code being compiled. This means, having the back-end as a library solution. This would automatically provide 100% compile-time code introspection. This

Re: D front-end in D for D

Am 14.07.2012 12:48, schrieb Gor Gyolchanyan: I just got an amazing thought. If we end up getting a D front-end in D, I think it would be possible to make the back-end in the same space as the code being compiled. This means, having the back-end as a library solution. This would automatically pro

Re: D front-end in D for D

On Sat, Jul 14, 2012 at 3:16 PM, Paulo Pinto wrote: > Am 14.07.2012 12:48, schrieb Gor Gyolchanyan: > > I just got an amazing thought. If we end up getting a D front-end in D, >> I think it would be possible to make the back-end in the same space as >> the code being compiled. This means, having

Re: D front-end in D for D

On 07/14/2012 01:29 PM, Gor Gyolchanyan wrote: It would also make run-time mixins possible, which is absolutely amazing. It is amazingly unsafe, because at runtime there is no distinction between strings generated by the program and strings created from input to the program.

Re: D front-end in D for D

On Sat, Jul 14, 2012 at 4:52 PM, Timon Gehr wrote: > On 07/14/2012 01:29 PM, Gor Gyolchanyan wrote: > >> >> It would also make run-time mixins possible, which is absolutely amazing. >> >> > It is amazingly unsafe, because at runtime there is no distinction > between strings generated by the progr

Re: D front-end in D for D

Run-time mixins can be used for incredibly powerful stuff, yet the same run-time mixins can be used for incredibly dangerous stuff. Just don't use them if you don't know exactly what you're doing. :-) I don't see any case where a "runtime-mixin" is the only solution (it's definitly the unsafest

Re: D front-end in D for D

On Jul 14, 2012 9:15 AM, "David" wrote: >> >> Run-time mixins can be used for incredibly powerful stuff, yet the same >> run-time mixins can be used for incredibly dangerous stuff. Just don't >> use them if you don't know exactly what you're doing. :-) > > > I don't see any case where a "runtime-m

Re: D front-end in D for D

On Sat, Jul 14, 2012 at 5:23 PM, Kevin Cox wrote: > > On Jul 14, 2012 9:15 AM, "David" wrote: > >> > >> Run-time mixins can be used for incredibly powerful stuff, yet the same > >> run-time mixins can be used for incredibly dangerous stuff. Just don't > >> use them if you don't know exactly what

Re: D front-end in D for D

On 14-07-2012 12:48, Gor Gyolchanyan wrote: I just got an amazing thought. If we end up getting a D front-end in D, I think it would be possible to make the back-end in the same space as the code being compiled. This means, having the back-end as a library solution. This would automatically provi

Re: D front-end in D for D

On Sat, Jul 14, 2012 at 6:35 PM, Alex Rønne Petersen wrote: > On 14-07-2012 12:48, Gor Gyolchanyan wrote: > >> I just got an amazing thought. If we end up getting a D front-end in D, >> I think it would be possible to make the back-end in the same space as >> the code being compiled. This means,

Re: D front-end in D for D

Am 14.07.2012 14:52, schrieb Timon Gehr: On 07/14/2012 01:29 PM, Gor Gyolchanyan wrote: It would also make run-time mixins possible, which is absolutely amazing. It is amazingly unsafe, because at runtime there is no distinction between strings generated by the program and strings created fr

Re: D front-end in D for D

On Sat, Jul 14, 2012 at 6:47 PM, dennis luehring wrote: > Am 14.07.2012 14:52, schrieb Timon Gehr: > > On 07/14/2012 01:29 PM, Gor Gyolchanyan wrote: >> >>> >>> It would also make run-time mixins possible, which is absolutely amazing. >>> >>> >> It is amazingly unsafe, because at runtime there i

Re: D front-end in D for D

Am 14.07.2012 15:23, schrieb Kevin Cox: On Jul 14, 2012 9:15 AM, "David" wrote: Run-time mixins can be used for incredibly powerful stuff, yet the same run-time mixins can be used for incredibly dangerous stuff. Just don't use them if you don't know exactly what you're doing. :-) I don't se

Re: D front-end in D for D

On 07/14/2012 04:44 PM, Gor Gyolchanyan wrote: On Sat, Jul 14, 2012 at 6:35 PM, Alex Rønne Petersen mailto:a...@lycus.org>> wrote: On 14-07-2012 12:48, Gor Gyolchanyan wrote: I just got an amazing thought. If we end up getting a D front-end in D, I think it would be

Re: D front-end in D for D

On Saturday, 14 July 2012 at 10:48:56 UTC, Gor Gyolchanyan wrote: I just got an amazing thought. If we end up getting a D front-end in D, I think it would be possible to make the back-end in the same space as the code being compiled. This means, having the back-end as a library solution. This w

Re: D front-end in D for D

On Sat, Jul 14, 2012 at 7:15 PM, Timon Gehr wrote: > On 07/14/2012 04:44 PM, Gor Gyolchanyan wrote: > >> On Sat, Jul 14, 2012 at 6:35 PM, Alex Rønne Petersen > > wrote: >> >> On 14-07-2012 12:48, Gor Gyolchanyan wrote: >> >> I just got an amazing thought. If we

Re: D front-end in D for D

On Sat, Jul 14, 2012 at 7:15 PM, Timon Gehr wrote: > On 07/14/2012 04:44 PM, Gor Gyolchanyan wrote: > >> On Sat, Jul 14, 2012 at 6:35 PM, Alex Rønne Petersen > > wrote: >> >> On 14-07-2012 12:48, Gor Gyolchanyan wrote: >> >> I just got an amazing thought. If we

Re: D front-end in D for D

On 07/14/2012 05:24 PM, Gor Gyolchanyan wrote: On Sat, Jul 14, 2012 at 7:15 PM, Timon Gehr mailto:timon.g...@gmx.ch>> wrote: On 07/14/2012 04:44 PM, Gor Gyolchanyan wrote: ... For instance, everybody seems to love hard-wiring the syntax into the language.

Re: D front-end in D for D

On Sat, Jul 14, 2012 at 7:36 PM, Timon Gehr wrote: > On 07/14/2012 05:24 PM, Gor Gyolchanyan wrote: > >> On Sat, Jul 14, 2012 at 7:15 PM, Timon Gehr > > wrote: >> >> On 07/14/2012 04:44 PM, Gor Gyolchanyan wrote: >> >> ... >> >> For instance, everybod

Re: D front-end in D for D

On 07/14/2012 05:28 PM, Gor Gyolchanyan wrote: On Sat, Jul 14, 2012 at 7:15 PM, Timon Gehr mailto:timon.g...@gmx.ch>> wrote: On 07/14/2012 04:44 PM, Gor Gyolchanyan wrote: On Sat, Jul 14, 2012 at 6:35 PM, Alex Rønne Petersen mailto:a...@lycus.org>

Re: D front-end in D for D

On 07/14/2012 05:42 PM, Gor Gyolchanyan wrote: On Sat, Jul 14, 2012 at 7:36 PM, Timon Gehr mailto:timon.g...@gmx.ch>> wrote: On 07/14/2012 05:24 PM, Gor Gyolchanyan wrote: On Sat, Jul 14, 2012 at 7:15 PM, Timon Gehr mailto:timon.g...@gmx.ch>

Re: D front-end in D for D

On 14/07/2012 15:33, Gor Gyolchanyan wrote: On Sat, Jul 14, 2012 at 5:23 PM, Kevin Cox mailto:kevincox...@gmail.com>> wrote: On Jul 14, 2012 9:15 AM, "David" mailto:d...@dav1d.de>> wrote: >> >> Run-time mixins can be used for incredibly powerful stuff, yet the same >> ru

Re: D front-end in D for D

On Saturday, 14 July 2012 at 13:33:16 UTC, Gor Gyolchanyan wrote: Yes, eval or exec is pretty much outlawed in other languages, I can only imagine the same would happen in D. That's a huge mistake a lot of people make. They outlaw things that they don't understand or don't know how to use.

Re: D front-end in D for D

On Sun, Jul 15, 2012 at 7:21 PM, SomeDude wrote: > On Saturday, 14 July 2012 at 13:33:16 UTC, Gor Gyolchanyan wrote: > >> >>> Yes, eval or exec is pretty much outlawed in other languages, I can only >>> imagine the same would happen in D. >>> >>> >> That's a huge mistake a lot of people make. They

Re: D front-end in D for D

On Saturday, 14 July 2012 at 15:18:53 UTC, David Piepgrass wrote: I think, for multiple reasons including this use case, D should have a "lightweight subset" with a smaller standard library and a somewhat simpler language definition (that retains most of D's power), which could shrink the siz