Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Control Flow

2 (2.2%)

Arrays, Strings, Pointers, and References

8 (9%)

Functions

4 (4.5%)

Basic object-oriented programming

30 (33.7%)

A bit more advanced OOP (Composition, Operator overloading, Inheritance, Virtual Functions)

18 (20.2%)

Templates

8 (9%)

Other (Explain)

4 (4.5%)

Working with files?  (Streams)

15 (16.9%)

Total Members Voted: 89

[Outcast Orange]

Thank you for the code post, Argembarger.
My eyes will have fun cutting through it with machetes and having a general sense of confusion.

Inform 7 seems amazing, but I can't figure out how to stack if statements.
If anyone wants to show me a working example of a three level deep if statement, I'd be very very grateful.

C++ example:

Code: [Select]

if(a==1){
   if(b==1){
      if(c==1){
          //blah
      }
   }
}

VB code:

Code: [Select]

if a = 1 then
     if b = 1 then
          if c = 1 then
             'blah
          end if
     end if
end if

Inform 7 code:

Code: [Select]

if the man has a sword then
     huh?

What I really don't want is any AND logic.
I can do AND just fine.

[Mondark]

Inform 7 seems amazing, but I can't figure out how to stack if statements.

I haven't really had to do this very much, since I can usually get the same result in a cleaner way by using scenes and rules, but I think you can use the 'begin' and 'end if' keywords to do this.

Code: [Select]

if [some condition] begin;
  if [other condition] begin;
  end if;
end if;


[Outcast Orange]

Sounds good.
I'll report back the results.

[qwertyuiopas]

Or you might need to use a colon at the end of the if statement. It's been a long time since I looked at it, though.

[Rose]

This game is notable in that it has the worst fucking gameplay ever. Just spam l until you find a goblin then spam k until it's dead. Rinse, repeat.

so it's a text based god of war then.

[alfie275]

Talking of Inform, I have the source to this story I started but never finished, if you want to dig through it for any useful crap:

Spoiler (click to show/hide)

"Timelord" by alfie275

The Past is a region.
The Future is a region.

The TDS is a region.

The Tardis Main Chamber is a room in the TDS."A large circular room with many curved pillars around it, in the middle is a console on a raised platform."

The player is in the Tardis Main Chamber.
The enterable supporter called the Tardis is in the Street.

TTR is a room.

The Street is a room in the Past. "A standard street with houses in neat rows. To the south is a small wooden shed."

The Ruined Street is a room in the Future. "The road is cracked and the houses have long fallen apart. To the south is a slight dip in the ground."

The Shed is a room in the Past.

The Ruined Shed is a room in the Future. "There is an odd dip in the ground, such as might be made from a collapsed vertical hole. A few rotten planks poke out of the ground."


The Ruined Shed is south of the Ruined Street.

The Shed door is a door.

The Shed door is north of the Shed.
The Shed door is south of the Street.
The Shed door is lockable and locked.

The Small metal box is a container in the Shed.
The Small metal box is lockable and locked.

The Rusted Box is a container in the Ruined Shed. "A rusted box, the lid has fallen off."
The Rusted Box contains a thing called the Rusted key.

The Rusted key unlocks the Shed door.



The Tardis Door is a door.
Tardis Door is lockable and locked.
Tardis Door is south of Tardis Main Chamber.
Tardis Door is north of TTR.

After going to TTR:
Move the player to the location of the Tardis.

After inserting something (called thing) into the Tardis:
Move the thing to Tardis Main Chamber;
say "You put [the thing] into the Tardis.".

Instead of inserting something into the Tardis when the Tardis Door is closed:
say "The door is closed";

The Glowing Key is a thing carried by the player.

The Glowing Key unlocks the Tardis Door.


The plank is a thing in the Ruined Street.

Inside the Tardis Main Chamber is a device called a Console.

procedural rule for inserting into the Tardis:
   ignore the Can't insert into what's not a container rule.

Instead of opening the Tardis:
   if the Tardis Door is locked:
      say "Its locked.";
   otherwise:
      if the Tardis Door is closed:
         say "You open the Tardis door.";
         change the Tardis Door to open;
      otherwise:
         say "It's already open".

Instead of closing the Tardis:
   if the Tardis Door is open:
      say "You close the Tardis door.";
      change the Tardis Door to closed;
   otherwise:
      say "It's already closed".


Instead of entering the Tardis:
   if Tardis Door is open:
      say "You walk through the door into the Tardis.";
      move the player to the Tardis Main Chamber;
   otherwise:
      say "The door is closed.";

Instead of locking the Tardis with the Glowing Key:
   if the Tardis Door is open:
      say "You must first close the Tardis.";
   otherwise:
      if Tardis Door is locked:
         say "It is already locked.";
      otherwise:
         say "You lock the Tardis.";
         now the Tardis Door is locked.

Instead of unlocking the Tardis with Glowing Key:
   if the Tardis Door is open:
      say "You must first close the Tardis.";
   otherwise:
      if Tardis Door is unlocked:
         say "It is already unlocked.";
      otherwise:
         say "You unlock the Tardis.";
         now the Tardis Door is unlocked.

Understand "Door" as Tardis.

After switching on the Console:
   say "There is a wheezing sound and a large rod moves up and down in the glass central pillar at the middle of the console. After a short while it stops.";
   now the Console is switched off;
   if the location of the Tardis is Ruined Street:
      Move the Tardis to the Street;
   otherwise:
      Move the Tardis to the Ruined Street.

[Mondark]

Nice Dr. Who setup there!  I like the idea of going into the broken down, future version of the shed to get the key that unlocks the past (unlooted) version.  It's a nice usage of the regions mechanism.

[lordnincompoop]

What would this do?

Code: [Select]

int main()
{
int naArray[1];
int nSize = 0;
do
{
naArray[nSize++] = 424242;
} while (nSize > 0);
return 0;
}

[qwertyuiopas]

That would probably segfault.


Because it is a do while loop, the size variable would be increased first, so it would repeat. It might overwrite the size variable itself, or it might not, but either way it would start writing somewhere it shouldn't. Unless it was carefully engineered to affect a specific memory location to do something useful, and in that case it would probably qualify as an IOCCC entry with little additional work.

[ILikePie]

I've tried messing around with bits today. Doing decimal to binary conversion, addition, etc.
Here's the addition function, which seems to break when calculating various numbers. 15 + 9 = 32, 15 + 15 = 128, 15 + 11 = 64, etc. (I've only noticed this happening with 15)

Code: [Select]

#include <stdio.h>
#include <stdlib.h>
#define BITS 8

int b_add (int left, int rght) {
  int ans[BITS],    // answer
    dec = 0,            // decimal value
    car = 0,        // carry
    l_bit,          // left bit
    r_bit,          // right bit
    i = 0,          // iterators:
    j = 1;          //
  // calculate:
  for (; i <= BITS-1; i++) {
    l_bit = (left & j) >> i;
    r_bit = (rght & j) >> i;
    j = j << 1;
    printf("l: %d  r: %d\n", l_bit, r_bit);
    if (car > 0 && l_bit == 0) {
      l_bit = 1;
      car--;
    }
    if (l_bit == 1) {
      if (r_bit == 1) {
        car++;
        ans[i] = 0;
      } else {
        ans[i] = (car > 0)? 0:1;
      }
    } else {
      ans[i] = l_bit | r_bit;
    }
  }
  // convert:
  i = 0;
  for  (; i <= BITS-1; i++) {
    dec = dec | (ans[i] << i);
  }
  // print:
  printf("result: ");
  i = BITS-1;
  for (; i >= 0; i--) {
    printf("%d", ans[i]);
  }
  printf(" -> %d\n", dec);
}
What baffles me though, is not what causes this (It's obviously the broken pseudo-carry), but why does it happen. Hopefully someone has the answer.

ps: the carry is broken because I tried writing this without looking at some solution, I didn't even know how to add when I started. instead of having left OR right OR carry, I have carry as the amount of times I still need to carry, then if left = 0, make it equal 1 and carry--.

[Siquo]

Code: [Select]

    if (car > 0 && l_bit == 0) {
      l_bit = 1;
      car--;   // here left = 1, carry becomes 0
    }


    if (l_bit == 1) {
      if (r_bit == 1) {
        car++;
        ans[i] = 0;
      } else {   // so if right =0 we end up here
        ans[i] = (car > 0)? 0:1; // What is this? We already used the carry to add to "left" I think this is breaking it.
      }
    } else {
      ans[i] = l_bit | r_bit;
    }
  }
}

Possible fix:
if (car > 0 && l_bit == 0) {
  l_bit = 1;
  car--;   // here left = 1, carry becomes 0
}
ans[i] = l_bit | r_bit;
if(l_bit && r_bit){ car++; }
But it's late and I might be mistaken.

[Outcast Orange]

Thank you for the inform code Alfie.
I couldn't figure out the syntax for some things so I copied some of yours.

[qwertyuiopas]

Here is an old one of mine from about a year ago. I started by trying to create a basic computer system that would be used as a major plot component. Unfortunately, I stopped, possibly because of laziness, possibly because of some difficult bit.

Spoiler (click to show/hide)

"Escape" by Me

Part 0 - Kinds

A terminal is a kind of thing. A terminal is either active or inactive. A terminal is usually inactive.


Part 1 - The code

Chapter 0 - The prologue

The prologue region is a region.

Skipping the prologue is an action applying to nothing.
Instead of skipping the prologue in the game region, say "The prologue is already over."
Instead of skipping the prologue in the prologue region, move the player to the main room.
Understand "skip prologue", "start game" and "start" as skipping the prologue.

Proceeding is an action applying to nothing.
Instead of proceeding in the game region, say "The prologue is already over, but if you need assistance, you can always try 'hint'."
Understand "proceed" and "continue" as proceeding.

Prologue_0 is a room in the prologue region. Prologue_0 has a printed name "". "There is an optional short, interactive, prologue sequence. If you would like to skip it, at any time during it, you may say 'skip prologue', 'start game', or 'start'.

The following sequence of rooms form a linear enviroment, purely to set the mood and hint at the setting. There is a turn-limit in each, and you can use 'proceed' or 'continue' to let the game select the right action for you to take." North of prologue_0 is prologue_1.

Instead of proceeding in prologue_0, try going north.

Chapter 1 - The actual game

The game region is a region.

The main room is a room in the game region. The main room has a printed name "".

A computer terminal is a terminal in the main room. It has a printed name "[if inactive]inactive [end if]computer terminal".

Activating is an action applying to one touchable thing.
Carry out activating the terminal:
   Say "You don't see a way, or even a need to activate [the noun]."
Understand "activate [the terminal]", "turn on [the terminal]", "turn [the terminal] on" as activating.

Instead of activating an active terminal, say "You don't see any need to turn it on when it already is on."
Instead of activating an inactive terminal:
   Change the noun to active;
   Say "You activate the terminal, and a prompt quickly appears, asking you if you want to login to an existing account, or create a new one."
   

Part 2 - Utilities and tables

Chapter 0 - tables

Table 0 - password characters
char
"a"
"b"
"c"
"d"
"e"
"f"
"g"
"h"
"i"
"j"
"k"
"l"
"m"
"n"
"o"
"p"
"q"
"r"
"s"
"t"
"u"
"v"
"w"
"x"
"y"
"z"
"0"
"1"
"2"
"3"
"4"
"5"
"6"
"7"
"8"
"9"
"_"

Table 1 - users
username      password
indexed text   indexed text
"admin"      "unknown"
With 20 blank rows.

Table 2 - folders
location      permission      name            path
text         number      text            text
"C:"         2            "users"            "C:\users"
"C:\users"      10            "admin"         "C:\users\admin"
With 100 blank rows.

Table 3 - files
location         permission   name
text            number   text
"C:\users\admin"   10         "ohai"
With 200 blank rows.

Chapter 2 - utilities

Understand "login", "log in", "logon", "log on" as logging in.

Logging in is an action applying to nothing.

Carry out logging in:
   say "There isn't a useable terminal in view to log in from."

Instead of logging in in the presence of an active terminal:
   change the command prompt to "Username:".
To randomize all passwords:
   repeat through the table of users:
      repeat with N running from 1 to the number of characters in the password entry:
         replace character number N in the password entry with (the char in row (a random number from 1 to the number of rows in the table of password characters) of the table of password characters);
   

To say the login failure:
   say "The username or password was incorrect. Please vertify you did not misspell either, and try again."

To show the directory prompt:
   change the command prompt to "[current directory]>"

To set the directory test:
   change the directory test to the terminal command;
   replace word number 1 in the directory test with "";
   replace character number 1 in the directory test with "";

After reading a command:
   If the command prompt is "Username:":
      change the current username to the player's command;
      change the command prompt to "Password:";
      rule succeeds;
   otherwise if the command prompt is "Password:":
      repeat through the table of users:
         if the current username is the username entry:
            change the current password to the player's command;
            if the current password is the password entry:
               say "Success!";
               Change the current directory to "C:\users\[current username]";
               Show the directory prompt;
               rule succeeds;
            otherwise:
               say the login failure;
               change the command prompt to ">";
               rule succeeds;
         otherwise:
            say the login failure;
      change the command prompt to ">";
      rule succeeds;
   otherwise if the command prompt is not ">":
      change the terminal command to the player's command;
      if (word number 1 in the terminal command) is "leave":
         change the command prompt to ">";
         rule succeeds;
      otherwise if (word number 1 in the terminal command) is "dir":
         repeat through the table of folders:
            if the current directory is the location entry:
               say the name entry;
         repeat through the table of files:
            if the current directory is the location entry:
               say the name entry;
         rule succeeds;
      otherwise if (word number 1 in the terminal command) is "cd":
         if (punctuated word number 2 in the terminal command) is "..":
            repeat through the table of folders:
               if the current directory is the path entry:
                  change the current directory to the location entry;
                  rule succeeds;
         set the directory test;
         say the directory test;
         repeat through the table of folders:
            say "([the directory test])([the path entry])([the name entry])";
            if "[the path entry]" exactly matches the text "[the directory test]", case insensitively:
               say "yay";
            if "[the name entry]" exactly matches the text "[the directory test]", case insensitively:
               say "yay2";
         rule succeeds;
      say "Invalid command.";
      rule succeeds;

The current username is indexed text that varies.
The current password is indexed text that varies.
The terminal command is indexed text that varies.
The current directory is indexed text that varies.
The directory test is indexed text that varies.

[When play begins:
   randomize all passwords;]

Yeah, it looks like I just quit in the middle of working on it, but there should be plenty of example syntax there.

[Outcast Orange]

That is all very interesting.

I've started a side project.
It will be crispy.

[Argembarger]

Woo I finally put the final touches to my Enigma encrypter/decrypter!

Err, I mean

j6`8   }   
@DH
N#&(V+'Y'4\,('.#c)3)9A9>0>|243CKCH:Hx