Google Treasure Hunt
-
http://treasurehunt.appspot.com/[^]
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 3 out now -
http://treasurehunt.appspot.com/[^]
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 3 out nowOk, before I give them my name and e-mail address: what is it?
Software Zen:
delete this;
Fold With Us![^] -
Ok, before I give them my name and e-mail address: what is it?
Software Zen:
delete this;
Fold With Us![^] -
Hmmm, that may help :) Here[^] is some more info.
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 3 out nowWell, I'm out already, since it involved intimate, shall we say biblical, knowledge of penguins...
Software Zen:
delete this;
Fold With Us![^] -
http://treasurehunt.appspot.com/[^]
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 3 out nowVery cool. My son and I just tried to answer one (unsuccessfully). On a related note, I wanted to write a little program to help with the calculations, since many of the answers are too big for calc.exe. :-O Upon finding the long-awaited BigInteger was dropped (or rather, made non-public) in .NET 3.5, I used Reflector to generate the source...and whammo, I've got a BigInteger type to use in my little puzzle-solving program. But here's the cool part that may indicate where Microsoft may be headed with C# 4 and .NET 4: the BigInteger type is decorated with several functional programming and design-by-contract attributes (which are also currently internal). For example, System.Core assembly, which contains much of the new LINQ functionality, contains [Pure], [Immutable] and several other attributes functional programmers might recognize. Also, BigInteger utilizes Contract.Ensures, Contract.Requires, and several others that indicate a design-by-contract programming direction. I predict C# 4 will utilize these by introducing some new keywords, and have the compiler check for errors at compile-time. Code will look like this:
[Pure]
double Foo(int i, string s)
requires i > 0
requires s != null
ensures return > 0;
{
...
}Interesting stuff...we shall see!
-
Very cool. My son and I just tried to answer one (unsuccessfully). On a related note, I wanted to write a little program to help with the calculations, since many of the answers are too big for calc.exe. :-O Upon finding the long-awaited BigInteger was dropped (or rather, made non-public) in .NET 3.5, I used Reflector to generate the source...and whammo, I've got a BigInteger type to use in my little puzzle-solving program. But here's the cool part that may indicate where Microsoft may be headed with C# 4 and .NET 4: the BigInteger type is decorated with several functional programming and design-by-contract attributes (which are also currently internal). For example, System.Core assembly, which contains much of the new LINQ functionality, contains [Pure], [Immutable] and several other attributes functional programmers might recognize. Also, BigInteger utilizes Contract.Ensures, Contract.Requires, and several others that indicate a design-by-contract programming direction. I predict C# 4 will utilize these by introducing some new keywords, and have the compiler check for errors at compile-time. Code will look like this:
[Pure]
double Foo(int i, string s)
requires i > 0
requires s != null
ensures return > 0;
{
...
}Interesting stuff...we shall see!
Very interesting! :cool:
Semicolons: The number one seller of ostomy bags world wide. - dan neely
-
Very cool. My son and I just tried to answer one (unsuccessfully). On a related note, I wanted to write a little program to help with the calculations, since many of the answers are too big for calc.exe. :-O Upon finding the long-awaited BigInteger was dropped (or rather, made non-public) in .NET 3.5, I used Reflector to generate the source...and whammo, I've got a BigInteger type to use in my little puzzle-solving program. But here's the cool part that may indicate where Microsoft may be headed with C# 4 and .NET 4: the BigInteger type is decorated with several functional programming and design-by-contract attributes (which are also currently internal). For example, System.Core assembly, which contains much of the new LINQ functionality, contains [Pure], [Immutable] and several other attributes functional programmers might recognize. Also, BigInteger utilizes Contract.Ensures, Contract.Requires, and several others that indicate a design-by-contract programming direction. I predict C# 4 will utilize these by introducing some new keywords, and have the compiler check for errors at compile-time. Code will look like this:
[Pure]
double Foo(int i, string s)
requires i > 0
requires s != null
ensures return > 0;
{
...
}Interesting stuff...we shall see!
Judah Himango wrote:
I predict C# 4 will utilize these by introducing some new keywords, and have the compiler check for errors at compile-time. Code will look like this:
:cool: C# gets significantly less crappy with every release. I'm impressed.
Citizen 20.1.01
'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
-
http://treasurehunt.appspot.com/[^]
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 3 out nowNooit! Far too much thinking for after midnight. :doh:
Semicolons: The number one seller of ostomy bags world wide. - dan neely
-
Well, I'm out already, since it involved intimate, shall we say biblical, knowledge of penguins...
Software Zen:
delete this;
Fold With Us![^]Gary R. Wheeler wrote:
I'm out already, since it involved intimate, shall we say biblical, knowledge of penguins...
Own up Gary, you know more about penguins than you are letting on! :laugh:
Simply Elegant Designs JimmyRopes Designs
Think inside the box! ProActive Secure Systems
I'm on-line therefore I am. JimmyRopes -
Judah Himango wrote:
I predict C# 4 will utilize these by introducing some new keywords, and have the compiler check for errors at compile-time. Code will look like this:
:cool: C# gets significantly less crappy with every release. I'm impressed.
Citizen 20.1.01
'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
It was ever crappy? :confused:
Semicolons: The number one seller of ostomy bags world wide. - dan neely
-
It was ever crappy? :confused:
Semicolons: The number one seller of ostomy bags world wide. - dan neely
I wouldn't call C# v1 crappy, but I would say C# 1 was a very basic, vanilla copy of Java, with a few niceties like properties and events. Releases since then have made some significant strides to fly above Java land, IMO.
-
It was ever crappy? :confused:
Semicolons: The number one seller of ostomy bags world wide. - dan neely
-
http://treasurehunt.appspot.com/[^]
xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 3 out now