Fredrik Lundh wrote:
> Antoon Pardon wrote:
>
> > One place where I would use such a feature is in a unittest
> > package. I think being able to write self.assert or self.raise
> > looks better than having to append an underscore.
>
> patch here:
>
> http://mail.python.org/pipermail/python-list/20
Roy Smith wrote:
>
> As I remember, you didn't need the whitespace either. IIRC, your example
> above could have been written as:
>
> PROGRAMKWDS
> REALREAL,WRITE
> WRITE=1.0
> REAL=2.0
> WRITE(*,*)WRITE,REAL
> END
>
It's stranger than that. FORTRAN 77 is in
Paul Rubin wrote:
> Antoon Pardon <[EMAIL PROTECTED]> writes:
> > This is just an idea of mine, nothing I expect python to adapt.
> > But just suppose the language allowed for words in bold. A word
> > in bold would be considered a reserved word, a word in non bold
> > would be an identifier.
>
> H
Carl Banks wrote:
> metaperl wrote:
> > --> python -i
> > >>> class = "algebra"
> > File "", line 1
> > class = "algebra"
> > ^
> > SyntaxError: invalid syntax
> > >>>
> >
> >
> > Why isn' t the parser smart enough to see that class followed by an
> > identifier is used for class
> One place where I would use such a feature is in a unittest
> package. I think being able to write self.assert or self.raise
> looks better than having to append an underscore.
Maybe that is a good argumment for Py.Test ;)
--
http://mail.python.org/mailman/listinfo/python-list
Cliff Wells wrote:
>> patch here:
>>
>> http://mail.python.org/pipermail/python-list/2001-June/047996.html
>
> Did you happen to remember this post or is Google *really* your friend?
Have you taken The Oath? If not, I'm afraid I cannot tell you.
--
http://mail.python.org/mailman/listinfo/pyt
On Wed, 2006-09-13 at 10:30 +0200, Fredrik Lundh wrote:
> Antoon Pardon wrote:
>
> > One place where I would use such a feature is in a unittest
> > package. I think being able to write self.assert or self.raise
> > looks better than having to append an underscore.
>
> patch here:
>
> http://ma
On 2006-09-13, metaperl <[EMAIL PROTECTED]> wrote:
> One way to avoid the issue I brought up is for the syntax to
> be very regular... like Lisp or Tcl:
>
> set class "algebra"
>
> (setq class "algebra")
Unfortunately (or fortunately?) the human mind isn't very
regular and seems to prefer structu
One way to avoid the issue I brought up is for the syntax to be very
regular... like Lisp or Tcl:
set class "algebra"
(setq class "algebra")
--
http://mail.python.org/mailman/listinfo/python-list
metaperl wrote:
> --> python -i
> >>> class = "algebra"
> File "", line 1
> class = "algebra"
> ^
> SyntaxError: invalid syntax
> >>>
>
>
> Why isn' t the parser smart enough to see that class followed by an
> identifier is used for class definition but class followed by equals is
Antoon Pardon wrote:
> One place where I would use such a feature is in a unittest
> package. I think being able to write self.assert or self.raise
> looks better than having to append an underscore.
patch here:
http://mail.python.org/pipermail/python-list/2001-June/047996.html
--
http://ma
On 2006-09-13, Paul Rubin wrote:
> Antoon Pardon <[EMAIL PROTECTED]> writes:
>> This is just an idea of mine, nothing I expect python to adapt.
>> But just suppose the language allowed for words in bold. A word
>> in bold would be considered a reserved word, a word in non bold
>> would be an ident
Antoon Pardon <[EMAIL PROTECTED]> writes:
> This is just an idea of mine, nothing I expect python to adapt.
> But just suppose the language allowed for words in bold. A word
> in bold would be considered a reserved word, a word in non bold
> would be an identifier.
Heh, sounds like ColorForth, in
On 2006-09-13, Carl Banks <[EMAIL PROTECTED]> wrote:
> metaperl wrote:
>> --> python -i
>> >>> class = "algebra"
>> File "", line 1
>> class = "algebra"
>> ^
>> SyntaxError: invalid syntax
>> >>>
>>
>>
>> Why isn' t the parser smart enough to see that class followed by an
>> identi
In article <[EMAIL PROTECTED]>,
"Carl Banks" <[EMAIL PROTECTED]> wrote:
> Alex Martelli wrote:
>
> > IBM (PL/I's inventor and rabid defender) found out the hard way that
> > making the parser more complicated, slow and bug-prone in order to allow
> > such absurd obfuscation was NOT a popular tra
Cliff Wells wrote:
> On Tue, 2006-09-12 at 18:05 -0700, Robert Hicks wrote:
> > metaperl wrote:
> > > Istvan Albert wrote:
> > > > metaperl wrote:
> > > > > --> python -i
> > > > > >>> class = "algebra"
> > > > > File "", line 1
> > > > > class = "algebra"
> > > > > ^
> > > > > Syn
Alex Martelli wrote:
> IBM (PL/I's inventor and rabid defender) found out the hard way that
> making the parser more complicated, slow and bug-prone in order to allow
> such absurd obfuscation was NOT a popular trade-off -- despite IBM's
> alleged monopoly power, PL/I is now basically dead while t
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Alex Martelli) wrote:
> metaperl <[EMAIL PROTECTED]> wrote:
>
> > Diez B. Roggisch wrote:
> > > metaperl schrieb:
> > > > --> python -i
> > > class = "algebra"
> > > > File "", line 1
> > > > class = "algebra"
> > > > ^
>
Steve Holden <[EMAIL PROTECTED]> wrote:
> Otherwise you could try and fix the error, like the PL/1 F-level
> compiler used to. This would usually work when all that was wrong was a
> missing semicolon, but it frequently went completely berserk in other
Ah, yeah, I forgot that particularly endear
metaperl <[EMAIL PROTECTED]> wrote:
> Diez B. Roggisch wrote:
> > metaperl schrieb:
> > > --> python -i
> > class = "algebra"
> > > File "", line 1
> > > class = "algebra"
> > > ^
> > > SyntaxError: invalid syntax
> > >
> > >
> > > Why isn' t the parser smart enough to see
metaperl <[EMAIL PROTECTED]> wrote:
Yes, keywords are always reserved. The one major language that tried to
do otherwise was PL/I, where you could code, e.g.:
if if = if then then = else else else = if
((of course, '=' was also polimorpically read as either assignment OR
comparison -- I gathe
metaperl wrote:
> --> python -i
> >>> class = "algebra"
> File "", line 1
> class = "algebra"
> ^
> SyntaxError: invalid syntax
> >>>
>
>
> Why isn' t the parser smart enough to see that class followed by an
> identifier is used for class definition but class followed by equals is
On Tue, 2006-09-12 at 18:05 -0700, Robert Hicks wrote:
> metaperl wrote:
> > Istvan Albert wrote:
> > > metaperl wrote:
> > > > --> python -i
> > > > >>> class = "algebra"
> > > > File "", line 1
> > > > class = "algebra"
> > > > ^
> > > > SyntaxError: invalid syntax
> > >
> > > De
metaperl wrote:
> Istvan Albert wrote:
> > metaperl wrote:
> > > --> python -i
> > > >>> class = "algebra"
> > > File "", line 1
> > > class = "algebra"
> > > ^
> > > SyntaxError: invalid syntax
> >
> > Designing a syntax to avoid all possible newbie errors is impractical
> > beca
metaperl wrote:
> Istvan Albert wrote:
>
>>metaperl wrote:
>>
>>>--> python -i
>>>
>>class = "algebra"
>>>
>>> File "", line 1
>>>class = "algebra"
>>> ^
>>>SyntaxError: invalid syntax
>>
>>Designing a syntax to avoid all possible newbie errors is impractical
>>because as soon a
Istvan Albert wrote:
> metaperl wrote:
> > --> python -i
> > >>> class = "algebra"
> > File "", line 1
> > class = "algebra"
> > ^
> > SyntaxError: invalid syntax
>
> Designing a syntax to avoid all possible newbie errors is impractical
> because as soon as you are finished with o
Diez B. Roggisch wrote:
> metaperl schrieb:
> > --> python -i
> class = "algebra"
> > File "", line 1
> > class = "algebra"
> > ^
> > SyntaxError: invalid syntax
> >
> >
> > Why isn' t the parser smart enough to see that class followed by an
> the few reserved words won't
Istvan Albert wrote:
> metaperl wrote:
> > --> python -i
> > >>> class = "algebra"
> > File "", line 1
> > class = "algebra"
> > ^
> > SyntaxError: invalid syntax
>
> Designing a syntax to avoid all possible newbie errors is impractical
> because as soon as you are finished with o
metaperl wrote:
> --> python -i
> >>> class = "algebra"
> File "", line 1
> class = "algebra"
> ^
> SyntaxError: invalid syntax
Designing a syntax to avoid all possible newbie errors is impractical
because as soon as you are finished with one iteration the new newbies
will start m
"metaperl" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Why isn' t the parser smart enough to see that class followed by an
> identifier is used for class definition but class followed by equals is
> a simple assignment?
Because it's simpler to reserve words than worry about po
metaperl schrieb:
> --> python -i
class = "algebra"
> File "", line 1
> class = "algebra"
> ^
> SyntaxError: invalid syntax
>
>
> Why isn' t the parser smart enough to see that class followed by an
> identifier is used for class definition but class followed by equals is
>
--> python -i
>>> class = "algebra"
File "", line 1
class = "algebra"
^
SyntaxError: invalid syntax
>>>
Why isn' t the parser smart enough to see that class followed by an
identifier is used for class definition but class followed by equals is
a simple assignment?
Also, I had
32 matches
Mail list logo
