> "RK" == Rob Kinyon <[EMAIL PROTECTED]> writes:
>> > Text-substitution macros would have to be handled in an earlier pass,
>>
>> I still don't see evidence for this. Or maybe I do, but I don't see
>> any reason that the preprocessing pass must finish before the parsing
>> begins.
> > Text-substitution macros would have to be handled in an earlier pass,
>
> I still don't see evidence for this. Or maybe I do, but I don't see
> any reason that the preprocessing pass must finish before the parsing
> begins.
Mixing C and Perl ...
my $foo;
BEGIN { $foo = '}'; }
#define OPEN {
On 10/18/05, Rob Kinyon <[EMAIL PROTECTED]> wrote:
> On 10/18/05, Uri Guttman <[EMAIL PROTECTED]> wrote:
> > my impression is that both styles are supported as you can return either
> > text or an AST (compiled code) from a macro.
>
> That sounds really ... inefficient. For that to work, you'd have
On 10/18/05, Uri Guttman <[EMAIL PROTECTED]> wrote:
> > "SL" == Stevan Little <[EMAIL PROTECTED]> writes:
>
> SL> On Oct 18, 2005, at 1:45 PM, Luke Palmer wrote:
>
> >> On 10/18/05, Rob Kinyon <[EMAIL PROTECTED]> wrote:
> >>
> >>> 3) Macros. Nuff said.
> >>>
> >>
> >> Not quite.
> "SL" == Stevan Little <[EMAIL PROTECTED]> writes:
SL> On Oct 18, 2005, at 1:45 PM, Luke Palmer wrote:
>> On 10/18/05, Rob Kinyon <[EMAIL PROTECTED]> wrote:
>>
>>> 3) Macros. Nuff said.
>>>
>>
>> Not quite. Lispish macros, that is, macros that let you look at what
>> you'
On Oct 18, 2005, at 1:45 PM, Luke Palmer wrote:
On 10/18/05, Rob Kinyon <[EMAIL PROTECTED]> wrote:
3) Macros. Nuff said.
Not quite. Lispish macros, that is, macros that let you look at what
you're expanding.
To further expand on this, they will be AST-manipulating macros (LISP
style)
On 10/18/05, Uri Guttman <[EMAIL PROTECTED]> wrote:
> i have an opportunity to get an email sent to the faculty of a top CS
> dept. my goal is to get internal support for a potential YAPC to be
> hosted there. so i want to present perl 6 to them in a way which will
> sell them on its academic and c
On 10/18/05, Rob Kinyon <[EMAIL PROTECTED]> wrote:
> 3) Macros. Nuff said.
Not quite. Lispish macros, that is, macros that let you look at what
you're expanding.
> 4) More declarative syntax. This is more of a handwavy, but the syntax
> feels (to me) as if it's more declarative than before. For
Some other features:
1) You can write your program in any combination of programming styles
and languages, as you see fit. Thus, you can use your OO library
written in Ruby, that really fast C routine, and your Perl code, all
in one place.
2) There are a large number of operators that support list
Uri,
Well, aside from what is actually *in* Perl 6 currently, there are a
number of interesting side projects, which may or may not get
included in the final language design. Such as:
On Oct 18, 2005, at 3:40 AM, Uri Guttman wrote:
the new OO design (stole the best from the rest and pe
i have an opportunity to get an email sent to the faculty of a top CS
dept. my goal is to get internal support for a potential YAPC to be
hosted there. so i want to present perl 6 to them in a way which will
sell them on its academic and cutting edge aspects. your mission is to
write some short (2
11 matches
Mail list logo
