Re: make == as = ?

From: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: make == as = ?
Date: 2004-04-13 16:47:02
Message-ID: 20040413093747.V50317@megazone.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


>
> Dear Stephan,
>
> > > For the class I have in mind, there are no corner cases, just concepts and
> > > basic practice. They are not going to be db developers, not even computer
> >
> > So no string comparisons? I know that's a mostly unused corner case and
> > all, but... ;)
>
> They survive to the idea that text/date/... are "basic" types in SQL.
> Maybe I'm lucky... they could prefer java references with new/equals...;-)
>
> If I take your example about details of && vs AND semantics, while
> teaching "programming concepts" I'm not going to discuss the fact that &&
> is shortcut by the evaluator, as this is very specific.
>
> I'm not planing my students to know what "i=++i+i++;" could mean.

And I wouldn't expect that in a programming concepts course. But, if
you're going to (for example) say that, "preincrement and postincrement
work exactly as in C," you've got to realize that there's a chance a
student will know that the i++ + ++i is undefined and expect it to be
undefined in the language you're talking about. That's the problem with
using shorthand phrases like "exactly in <X>" without the "except ..."

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dennis Bjorklund 2004-04-13 16:57:48 Lexing with different charsets
Previous Message Peter Eisentraut 2004-04-13 16:36:07 Re: sql92 character sets