Re: [BUG] can not use op names as sub/method name

2004-03-14 Thread Leopold Toetsch
Jens Rieks [EMAIL PROTECTED] wrote: Hi, On Saturday 13 March 2004 07:28, Leopold Toetsch wrote: Jens Rieks [EMAIL PROTECTED] wrote: .sub open method Or, maybe .sub foo method as an alternative syntax? This would allow other characters than now in sub names, too. I've now allowed

Re: [BUG] can not use op names as sub/method name

2004-03-13 Thread Jens Rieks
Hi, On Saturday 13 March 2004 07:28, Leopold Toetsch wrote: Jens Rieks [EMAIL PROTECTED] wrote: Hi, .namespace [Source] .sub open method .pcc_begin_return .pcc_end_return .end fails with error:imcc:parse error, unexpected PARROT_OP, expecting IDENTIFIER Parrot opcode names

[BUG] can not use op names as sub/method name

2004-03-12 Thread Jens Rieks
Hi, .namespace [Source] .sub open method .pcc_begin_return .pcc_end_return .end fails with error:imcc:parse error, unexpected PARROT_OP, expecting IDENTIFIER jens

Re: [BUG] can not use op names as sub/method name

2004-03-12 Thread Leopold Toetsch
Jens Rieks [EMAIL PROTECTED] wrote: Hi, .namespace [Source] .sub open method .pcc_begin_return .pcc_end_return .end fails with error:imcc:parse error, unexpected PARROT_OP, expecting IDENTIFIER Parrot opcode names are basically reserved words. There are some exceptions, where the lexer