KennyTM~ wrote:
Bruno Medeiros wrote:
Simen Kjaeraas wrote:
As an example, while I'd enjoy seeing code like this, I'm not sure
I'd enjoy writing it (Note that I am prone to exaggerations):
int a = ∅; //empty set, same as = void
int[] b = [1,2,3,4,5,6];
a = readInt();
Hum, interesting
Bruno Medeiros wrote:
Andrei Alexandrescu wrote:
Spacen Jasset wrote:
Bill Baxter wrote:
On Thu, Oct 23, 2008 at 7:27 AM, Andrei Alexandrescu
[EMAIL PROTECTED] wrote:
Please vote up before the haters take it down, and discuss:
Andrei Alexandrescu wrote:
Bruno Medeiros wrote:
Andrei Alexandrescu wrote:
Spacen Jasset wrote:
Bill Baxter wrote:
On Thu, Oct 23, 2008 at 7:27 AM, Andrei Alexandrescu
[EMAIL PROTECTED] wrote:
Please vote up before the haters take it down, and discuss:
On Mon, 27 Oct 2008 00:41:26 +0100, Bill Baxter [EMAIL PROTECTED] wrote:
Same thing goes for downs' in-fix operators. I think his syntax is
/infix/ which means that his ops always have the same precedence as
division.
I'm guessing this Python Cookbook recipe is very similar to Downs'
technique.
On Mon, Oct 27, 2008 at 9:04 AM, Andrei Alexandrescu
[EMAIL PROTECTED] wrote:
What's the precedence of your user-defined in-fix operator?
--bb
Yup, I realized this myself as well. Seemed like such a great idea when I
only thought of it for three seconds. :p
An operator could always be
Bill Baxter wrote:
On Mon, Oct 27, 2008 at 11:43 AM, Andrei Alexandrescu
[EMAIL PROTECTED] wrote:
Bill Baxter wrote:
On Mon, Oct 27, 2008 at 9:04 AM, Andrei Alexandrescu
[EMAIL PROTECTED] wrote:
What's the precedence of your user-defined in-fix operator?
--bb
Yup, I realized this myself as
Reply to dsimcha,
Yes, I realize that it's best to do things like this off the
newsgroup, but your email address doesn't seem to work.
Sorry. I figure I get enough SPAM as it is. Besides, there are about 2 dozen
other ways to get it if you are persistent enough
Oh. Your in, have fun
(I
