The Big Programming Thread - Page 398

On November 22 2013 10:47 sluggaslamoo wrote:


Man I nearly finished writing my reply and then my computer crashed T_T, time to write it all again.

Anyway I looked at your original post again and I think I get it now. There is an initial array of 21 rooms, and each element has another array of 3 elements, which contain the index of the rooms in the original array.

Anyway I've found that telling people that their method is wrong never gets us anywhere so lets do it your way, then we'll design the program in a way that gives it enough flexibility that you can change it later if you want to.

Because you are using C, we'll use a mixture of object pool and factory patterns which makes life easier when using C. Also just because we are using C doesn't mean we can't take anything from OOP.

So initially we will need a Room Manager which is responsible for managing all your rooms and handling room instantiation. Your Room Manager will need
- object pool [base array]
- number_of_rooms [variable]
- initialize_rooms
- clean_up function [for use at the end of the program]
- create_room [factory function]
- has_room_available [true/false]
- retrieve_room

So first of all create those functions with no implementation, and your base array.

We don't need to use ADTs (classes for C), this can just be a separate file, or hell just separate it with comment lines for now.

####### Room Manager ######
function XYZ ()
etc etc
###########################

In your mind its important that you see these functions as belonging to a separate entity even if in reality they are global and don't belong to anything, it will make life easier in the long run.

Create your base array (object pool) globally (yes global variables are poisonous in a vacuum but lets not go down that path for now). Its not a real object pool (it contains arrays not objects) but we can treat it like one because it can be later.

In your initialize_rooms function this will create the pool. It should take a number_of_rooms argument which determines the size of the pool (base_array). Implement this first and test that it works (on its own), once it works move on.

In your clean_up function create an implementation that deallocates the array. This will eventually go at the end of your program.

In your has_room_available function, it will tell you if there are any empty rooms left in the pool. Basically you need to check if number_of_rooms doesn't exceed the number of rooms in the array, returning true or false. Test to make sure this works (on its own), then move on.

In your create_room function, it will take room1_number, room2_number, room3_number. Use your has_room_available() function to determine if you can create more rooms, if not, throw an error. It will then create an array in the next element in pool with 3 elements (using the arguments provided) using the number_of_rooms variable. When the array is created, the function returns the index of the room in the pool that was just created. Test to make sure this works (on its own), then move on.

In your retrieve_room function, you will just take a room_number argument. This will return the array from the pool, given the appropriate room index. This will also allow you to use a 1 based instead of 0 based numbering system, if you wanted to. Test to make sure this works, then move on.

Ok if you have unit tested your Room Manager (even just manually using traces), then you should be able to put the pieces the puzzle together without much problem knowing that each function on its own won't be causing errors allowing you to home in on any bugs much faster.

*************** Rooms done!

Now for the Player. We do the same thing, without using datastructures we create some variables for the player. Create another "component" for the Player like we did with the Room Manager.

Player
- player_position variable = Room number he is in
- move_to(room_number) = self explanatory
- current_room() = actually retrieves the room he is in using the retrieve_room function

See if you can implement those, remember to test each function separately. This is also where you can output your text adventure logging. "You enter room XYZ which room do you want to go now?"

************** Player done!

The last component for our minimum viable product will be the controller. Much like a gamepad, the controller is the interface responsible for handling all the input.

wait_for_input() will pause the terminal to wait for input using your terminal read function and return the appropriate data for which other components will use.

*************

The last bit comes with actually implementing the program. These components should be able to give you the tools to easily create a working program and in a very clean manner too.

The program should look something like

initialize_rooms(21)
starting_room = create_room(1,2,3)
create_room(starting_room,3,4)
move_to(starting_room)

while running
  wait_for_input()

clean_up()

*************

Now you may ask why you can't just throw everything in the main function and try and get it to work? Doing it this way gives you direction and prevents you from getting lost, even if you are writing more code, what takes time is not writing the code, its understanding the implementation.

If you can write 75 words per minute, chances are the time spent figuring out what to do is going to be the biggest bottleneck in your program implementation time. So next time instead of rushing into the implementation take a step back and have a think about what are the tools you need to make it work.

At first it will take a long time to do it this way, but eventually in the long run it will be much more efficient, I didn't stop to think one time during this whole post, I just wrote everything off the top of my head. There could be stuff missing, but it should be enough for you to fill in the gaps.

Because this implementation is flexible, if you ever decide to, you can have your Room Manager return data structures instead of arrays if you ever want a more complex program, without much effort.

    /*
        This is a basic room!
        Written by Drakkos.
        29/09/2000
    */

    inherit "/std/room";

    void setup() {
        set_short("blobby lair");
        set_long("This is where the grey blob lives. All around lie "
            "frogs, and wombles, and strange oozy things. It's a "
            "very nice lair, as lairs go.\n");
        add_property("determinate", "a ");
        set_light(50);
        add_item("frog", "The frogs are very nice. Very froggy.");
        add_item("womble", "It's Uncle Bulgaria!");
        add_item("strange oozy things", "Ewww!");

        add_exit("east", "/w/your_name/workroom", "road");
    }

    void reset() {
        call_out ("after_reset", 3);
    }

    void after_reset() {

        object ob = find_object("/w/your_name/simple_npc");

        // if (!ob) will return true if ob is 0... in other words, it
        // didn't find an object with find_object().

        if (!ob) {
        // There's no object with that filename loaded, so we load it
        // and then move it into this_object()... which in the case of
        // this example, is the room we just coded.

            ob = load_object("/w/your_name/simple_npc");

            // For information on how the move() function works, you
            // can check out 'help move'. But briefly, the first argument
            // is where the object is to be moved to... the second is the
            // message that objects in the destination get when the object
            // enters. $N will be replaced with the short of the object.
            // 'appear$s' is a pluralisation code... it will change to
            // 'appear' when more than one object enters at the same time,
            // and 'appears' when only one enters.

            ob->move(this_object(), "$N appear$s with a wet squelch.");

        }

        // if (!environment(ob)) will return true if ob returns 0 for
        // environment... in other words, it's loaded, but located in
        // null-space.

        else if (!environment(ob)) {
            ob->move (this_object(), "$N appear$s with a wet squelch.");
        }

    }

On November 23 2013 20:50 berated- wrote:


This is something I've always been intrigued by. When most go into compsci I think it's usual to want to work for one of the big guys. However, how many people in this thread actually do so?

The more I get into my career, the more happy I am to work for a small company. I get to directly impact the direction of the development, introduce new techs and ideas, and not have to go through layers of red tape to do so. Most of all, I'm considered an important part of the company...that seems like it would be way harder to achieve at a massive company.

On November 23 2013 05:36 darkness wrote:
To the guys doing Software Engineering, have you guys taken a masters degree? I currently can't afford masters if I don't have a gap year to earn some money. But then again, I'm not sure if I'm motivated that there is a good reason to do so. I guess if there's a programming related reward, then I might be more motivated.

On November 24 2013 03:15 billy5000 wrote:


I specifically mentioned that it doesn't have to be big as microsoft or google, but it doesn't hurt to aim larger it seems like. But anyway, the reason why I don't want to work at a small company is that they can't afford to invest a lot in training, which I think is significant as my first job into this field. So yeah, I do agree small companies aren't all that bad, but I think starting out in bigger companies has more value.

On November 23 2013 20:50 berated- wrote:


This is something I've always been intrigued by. When most go into compsci I think it's usual to want to work for one of the big guys. However, how many people in this thread actually do so?

The more I get into my career, the more happy I am to work for a small company. I get to directly impact the direction of the development, introduce new techs and ideas, and not have to go through layers of red tape to do so. Most of all, I'm considered an important part of the company...that seems like it would be way harder to achieve at a massive company.

On November 23 2013 20:50 berated- wrote:


This is something I've always been intrigued by. When most go into compsci I think it's usual to want to work for one of the big guys. However, how many people in this thread actually do so?

The more I get into my career, the more happy I am to work for a small company. I get to directly impact the direction of the development, introduce new techs and ideas, and not have to go through layers of red tape to do so. Most of all, I'm considered an important part of the company...that seems like it would be way harder to achieve at a massive company.

On November 24 2013 03:15 billy5000 wrote:


I specifically mentioned that it doesn't have to be big as microsoft or google, but it doesn't hurt to aim larger it seems like. But anyway, the reason why I don't want to work at a small company is that they can't afford to invest a lot in training, which I think is significant as my first job into this field. So yeah, I do agree small companies aren't all that bad, but I think starting out in bigger companies has more value.

The more I get into my career, the more happy I am to work for a small company. I get to directly impact the direction of the development, introduce new techs and ideas, and not have to go through layers of red tape to do so. Most of all, I'm considered an important part of the company...that seems like it would be way harder to achieve at a massive company.

On November 24 2013 03:15 billy5000 wrote:


I specifically mentioned that it doesn't have to be big as microsoft or google, but it doesn't hurt to aim larger it seems like. But anyway, the reason why I don't want to work at a small company is that they can't afford to invest a lot in training, which I think is significant as my first job into this field. So yeah, I do agree small companies aren't all that bad, but I think starting out in bigger companies has more value.

On November 24 2013 04:26 phar wrote:
Sure, if you value being the go-to guy for everything in your company, that's gonna be hard at a large company unless you're a Jeff Dean level of genius. But it's surprisingly not that difficult to carve out areas and become a local expert on certain things. The other advantage about a large place is that you have way more opportunities to learn. Being surrounded by a large number of really smart co-workers is a good way to get pulled up quickly.

On November 24 2013 04:26 Millitron wrote:

I never really thought about what kind of company I wanted to work for, because it doesn't matter too much to me. I just want to work on projects I'm passionate about.

On November 24 2013 05:09 Hobbesander wrote:
As a final note, I don't think most places have not stopped hiring for 2014 internships. Google's deadline is coming up, but I found multiple internships much later in the year (both at large and small companies). Apply ASAP, but spots are definitely open. I have my current job because of an internship I applied for in March.

1.Enumerate all empty cells in typewriter order (left to right, top to bottom)

2.Our “current cell” is the first cell in the enumeration.

3.Enter a 1 into the current cell. If this violates the Sudoku condition, try entering a 2, then a 3, and so forth, until
a. the entry does not violate the Sudoku condition, or until
b. you have reached 9 and still violate the Sudoku condition.

4.In case a: if the current cell was the last enumerated one, then the puzzle is solved. If not, then go back to step 2 with the “current cell” being the next cell.
In case b: if the current cell is the first cell in the enumeration, then the Sudoku puzzle does not have a solution. If not, then erase the 9 from the corrent cell, call the previous cell in the enumeration the new “current cell”, and continue with step 3.

On November 24 2013 06:39 darkness wrote:
1.Enumerate all empty cells in typewriter order (left to right, top to bottom)

2.Our “current cell” is the first cell in the enumeration.

int currentRow = QueryCurrentRow();
int currentColumn = QueryCurrentColumn();
int maxRows = QueryRows();
int maxColumns = QueryColumns();

for (int x = currentRow; x < maxRows; x += 1)
{
    for (int y = currentColumn; y < maxColumns; y += 1)
    {
        if (cellEmpty)
        {
            DoStuff();
        }
    }
}

On November 24 2013 09:13 Arnstein wrote:
Cygwin has bugged out, so I downloaded gVim Easy to use that instead. But it starts in insert mode, and esc doesn't make you go into command mode. How do I get to command mode?

On November 23 2013 14:35 Millitron wrote:

Your curriculum should have something called Software Engineering, or something similar. The class should include a big project where you work with others. May or may not do any actual coding in it, it could be just drawing up design documents and such.

On November 24 2013 11:04 Ben... wrote:
Was going to say the same thing. My university definitely has that and most of the other universities I have checked out have it too. I am planning on taking it next year no matter how much I will hate it because I know all of the companies here do a lot of team stuff so having that class will be important (also, not a ton of people seem to take it since it isn't mandatory but it seems like it would be so important). The prof who teaches it is teaching me in a different class right now and he is really good so that makes me a lot less apprehensive about taking the course. I could have technically taken it next term but I want another year of programming on my own under my belt before I start working with others so I don't cause issues, though from what I can tell, I am ahead of many of the other students in my year (Let's just say I'm not shocked that half the people this year will drop out by the end. Some of the mistakes and questions I see are kinda embarrassingly bad. Like people asking how to use ssh when we were supposed to use it all term for doing certain things in my one class or other people seeming like they need their hand held for absolutely everything. You'd think if someone was in Comp Sci they would have a certain degree of proficiency on a computer but apparently that isn't the case).

I'm in the same situation in that I switched majors to comp sci from math but because of how the class scheduling is set up it will take me 3 years to finish. I am fine with that though, I'd rather take things a little slower and learn everything more in depth than try and cram everything in and just squeeze by and not learn much because I have to rush everything. That's not to say next term won't be hell with 5 comp sci classes.

On November 23 2013 07:19 3FFA wrote:
Hehe thanks for the effort slug but you apparently need to re-read this part again.


I used C + Obj.C last year, this year I'm using Java, although the process I'm using is about the same as the one you outlined, so no worries. I just haven't learned data structures yet, although I believe that next year we will learn about them and my teacher will have us change this lab accordingly.