Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Google Treasure Hunt

Google Treasure Hunt

Scheduled Pinned Locked Moved The Lounge
phpvisual-studiocom
13 Posts 7 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L leppie

    Hmmm, that may help :) Here[^] is some more info.

    xacc.ide - now with TabsToSpaces support
    IronScheme - 1.0 alpha 3 out now

    G Offline
    G Offline
    Gary R Wheeler
    wrote on last edited by
    #4

    Well, I'm out already, since it involved intimate, shall we say biblical, knowledge of penguins...

    Software Zen: delete this;
    Fold With Us![^]

    J 1 Reply Last reply
    0
    • L leppie

      http://treasurehunt.appspot.com/[^]

      xacc.ide - now with TabsToSpaces support
      IronScheme - 1.0 alpha 3 out now

      J Offline
      J Offline
      Judah Gabriel Himango
      wrote on last edited by
      #5

      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!

      B S 2 Replies Last reply
      0
      • J Judah Gabriel Himango

        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!

        B Offline
        B Offline
        Brady Kelly
        wrote on last edited by
        #6

        Very interesting! :cool:

        Semicolons: The number one seller of ostomy bags world wide. - dan neely

        1 Reply Last reply
        0
        • J Judah Gabriel Himango

          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!

          S Offline
          S Offline
          Shog9 0
          wrote on last edited by
          #7

          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.'

          B 1 Reply Last reply
          0
          • L leppie

            http://treasurehunt.appspot.com/[^]

            xacc.ide - now with TabsToSpaces support
            IronScheme - 1.0 alpha 3 out now

            B Offline
            B Offline
            Brady Kelly
            wrote on last edited by
            #8

            Nooit! Far too much thinking for after midnight. :doh:

            Semicolons: The number one seller of ostomy bags world wide. - dan neely

            1 Reply Last reply
            0
            • G Gary R Wheeler

              Well, I'm out already, since it involved intimate, shall we say biblical, knowledge of penguins...

              Software Zen: delete this;
              Fold With Us![^]

              J Offline
              J Offline
              JimmyRopes
              wrote on last edited by
              #9

              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

              1 Reply Last reply
              0
              • S Shog9 0

                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.'

                B Offline
                B Offline
                Brady Kelly
                wrote on last edited by
                #10

                It was ever crappy? :confused:

                Semicolons: The number one seller of ostomy bags world wide. - dan neely

                J S 2 Replies Last reply
                0
                • B Brady Kelly

                  It was ever crappy? :confused:

                  Semicolons: The number one seller of ostomy bags world wide. - dan neely

                  J Offline
                  J Offline
                  Judah Gabriel Himango
                  wrote on last edited by
                  #11

                  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.

                  1 Reply Last reply
                  0
                  • B Brady Kelly

                    It was ever crappy? :confused:

                    Semicolons: The number one seller of ostomy bags world wide. - dan neely

                    S Offline
                    S Offline
                    Shog9 0
                    wrote on last edited by
                    #12

                    Pretty much what Judah said. C# 1.0 was... well, at best it was uninteresting. C# 2.0 and 3.0 demonstrated they were learning from Java's mistakes.

                    Citizen 20.1.01

                    'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'

                    1 Reply Last reply
                    0
                    • L leppie

                      http://treasurehunt.appspot.com/[^]

                      xacc.ide - now with TabsToSpaces support
                      IronScheme - 1.0 alpha 3 out now

                      S Offline
                      S Offline
                      Sam Slade
                      wrote on last edited by
                      #13

                      :confused:...has anyone got a clue about how to solve these? I submitted an answer and was vastly out, now i've got to calculate paths through a grid 68 by 35 moving right and down only...:mad:

                      1 Reply Last reply
                      0
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • World
                      • Users
                      • Groups