OCUK programming project?

Apart from the dangerous maintenance, it's also difficult to maintain. Headache inducing and usually unecessary. Also takes a lot of memory, tco or not. :)
 
Apart from the dangerous maintenance, it's also difficult to maintain. Headache inducing and usually unecessary. Also takes a lot of memory, tco or not. :)
it's how your braught up, persnally i learned recursion from K&R saying it was a elegant solution which got me interested. Most tco tends to stop the stack frames from building up, so not much memory loss there.

Things like tree treversing, parsing, and divide & conquer algorithms are much more elegant recursive. Espically tree traversing. Basic loops are better iterative, but acutal real world data structures like trees feel better parsed recursive.
 
Last edited:
it's how your braught up, persnally i learned recursion from K&R saying it was a elegant solution which got me interested. Most tco tends to stop the stack frames from building up, so not much memory loss there.
Memory is still used during the lookups before any "real" computation even begins. This is avoided somewhat when not using recursion, and using (for example) iterative measures such as here.
Things like tree treversing, parsing, and divide & conquer algorithms are much better recursive. Espically tree traversing.
That is purely subjective. I disagree, and much prefer managed lists for traversing (see Iterative Traversing).

I think we're taking this off topic now. :)
 
Recursive traversing is more concise, and subjectivly more unstandable than iterative in those examples. Tree treversing is pretty much always taught recursive, since that's pretty much the natural way of thinking about it.

The memory difference is neglible, for the added readbillity for divide and conquer things like quicksort.

But this tends to be a computer science vs Software engineering subject.

Yes this has been taken off topic a bit. I was just asking for feedback on python for the project, how did we get to this? :P
Feedback from someone who acutally knows the language? Not just blanket statements like avoid it?
 
Last edited:
You statically type everything, and manually deep copy for dymanic deep copy for assignments? You don't know how many bugs i have encounted with classes with member pointers all pointing to the same class because of a shallow copy due to the complier defined copy operator. Dangerous bugs to because they might not get caught by your test suite, until there in production.
Er. no, I didn't say that. I'm very happy to use deep copy, copy constructors and so forth where necessary, but not out of some religious desire. There's very little point doing those things with a singleton, for example.

Ah, the old recursive vs iterative debate. There's very little that gets programmers quite so defensive as that one. Personally - horses for courses. I've used both, consider both to have advantages and disadvantages, and leave it at that. I don't understand why programmers get so uptight about what is simply a design pattern - and one of many.

I'm probably not going to be popular when I point out that deep copy is, in fact, recursive.

As for Python, I might be confusing it with Perl, but I don't think so. IIRC, one of them is particularly nasty with even silly little things like formatting.
 
I think you need to seriously think about whether this project is actually going to be accessible for newbies - a lot of this discussion is really over my head, and I'm sure I'm not the only one who doesn't have a clue what 'dynamic deep copy for assignments' means.
I fear this is moving away from a community project where beginners can learn some programming alongside the more experienced guys, into something only pros will be able to contribute to.
 
I think you need to seriously think about whether this project is actually going to be accessible for newbies - a lot of this discussion is really over my head, and I'm sure I'm not the only one who doesn't have a clue what 'dynamic deep copy for assignments' means.
I fear this is moving away from a community project where beginners can learn some programming alongside the more experienced guys, into something only pros will be able to contribute to.

take no notice dude, they are just looking at who's the more alpha ;)

You dont need to know any code to be involved, concept design for example only requires a good idea and is just as important as the code itself.
 
I'd like to join this if you'll have me. know some PHP,MySQL, javascript, VB6 (!), Director/Lingo, coldfusion. So anything i can have a go at id be happy with. I made a space invaders type game at uni that i loved doing in director. May be nice to get a way from webforms that i mainly have to do now.
(what do i need to do)
 
forgive me if this sound abit too negative but all of these ideas seems abit too complex. if you guys start off small and find out who are the people willing to spend the most time and their skill levels then you could probably move on and work on something abit bigger/harder.

or even better, how about finding an open source project that all of you can agree to work on and contribute to that. at least they would have had a direction and management set in place already
 
That's what is also under discussion agent_paul, and us 'verterans' are throwing our weight around by 'upping' the topic all the time :p
 
forgive me if this sound abit too negative but all of these ideas seems abit too complex. if you guys start off small and find out who are the people willing to spend the most time and their skill levels then you could probably move on and work on something abit bigger/harder.

or even better, how about finding an open source project that all of you can agree to work on and contribute to that. at least they would have had a direction and management set in place already

lol I am unsure how they would take it - like a hostile take over or something lol - would be funny letting them know we are helping...

"hey, me and my friends like your project and wanna help out can we?"

"um ok, whats your skill sets?"

"everything."

"everything?"

"EEEEEEEVERYTHING!"

*10 minutes later the package has been downloaded 3000 times and is already past alpha testing.*

"What have you done!?"

"EEEEEEEEEEVERYTHIIIIIIIIIIIIIIING!!!! Grease grease, grease g-grease lightning, grease grease, grease g-grease lightning.... (breaks into song and dance)!"
 
lol I am unsure how they would take it - like a hostile take over or something lol - would be funny letting them know we are helping...

"hey, me and my friends like your project and wanna help out can we?"

"um ok, whats your skill sets?"

"everything."

"everything?"

"EEEEEEEVERYTHING!"

*10 minutes later the package has been downloaded 3000 times and is already past alpha testing.*

"What have you done!?"

"EEEEEEEEEEVERYTHIIIIIIIIIIIIIIING!!!! Grease grease, grease g-grease lightning, grease grease, grease g-grease lightning.... (breaks into song and dance)!"

lol, for some reason i have a feeling it'll be more like...

commit, commit, commit, commit... rev version +xxxxxxxx

checkout
build
build failed.

OH NO. ITS BROKEN! EVERYONE MAKE A RUN FOR IT!!!
 
If it is still proving difficult to decide on a project, why not choose something that you can benefit from yourselves? Everyone wants to make a game, but tbh.. it's a PITA.

Why not choose something like an Agile/KanBan/Scrum taskboard app or similar, so once released you can instantly benefit from it yourselves and use it for other projects?
 
Some of the things determined in the meeting we had on Tuesday were what general path we wanted to follow. We got a majority vote on a 2D game, so that is, as far as I know, is what we will choose. The other thing we discussed was the method on how to choose which project concept we will follow.

Currently we are submitting ideas for discussion/debate to be improved on and such, then a small group of members are to discuss the benefits and pitfalls as objectively as possible of each suggestion and essentially decide upon which of the projects we should do. Then when that's sorted we will discuss how to implement the project (we're also having a team to research the best language/library solution for the project).

I think, in my opinion, we have a reasonably clear direction as to where this is headed in terms of deciding what we're doing and how to go about it. It's early days though.

I think most of use would be happy to work on any of the suggested project concepts so far, it's just a matter of choosing the most appropriate one.
 
Hey all,

Sorry been at work all day so I clearly not been on here or the game's forum. I'll try and catch up with everything before heading out to watch the footy later!

EDIT: On the language engine selection issue can I ask people to post on this on the forum under "programming" Feel free to add your 2p worth backing the language you like, but if I could ask you to flag up in particular why it'd be the a good choice for 2D graphics. I think on some of the comments I've seen on here are bit off - those decisions there made in the meeting where all fully respecting the views of those in the meeting, if you want to have a say on what direction we take then participate in them (surely that makes sense to everyone).

Anyhow loving the concepts section :)
 
Last edited:
a quick 2p from me.. drop this concept of "teams" people will naturally fall into their preferred roles anyway, and leaving everything up to votes will prove more result worthy. A select few may not decide what is best for the whole, but asking the whole will. :) Havign a mail-list (if you haven't already got one) will be your most valuable tool. A forum is nice to have, but requires people check it. Mail-lists get sent, and are quicker to reply to. :)

Have a few members (who are willing) to deal with impediments that the community may have. Disputes, split decisions etc.
 
can i just check will this be using stuff that i can get for free or will i have to buy the programming platform?

What language we're going to be using is being debated on the forum at the moment. But I think it's highly unlikely we'll choose something non-free.
 
a quick 2p from me.. drop this concept of "teams" people will naturally fall into their preferred roles anyway, and leaving everything up to votes will prove more result worthy. A select few may not decide what is best for the whole, but asking the whole will. :) Havign a mail-list (if you haven't already got one) will be your most valuable tool. A forum is nice to have, but requires people check it. Mail-lists get sent, and are quicker to reply to. :)

Have a few members (who are willing) to deal with impediments that the community may have. Disputes, split decisions etc.

Thanks for those comments jester. I can't really respond right now as I'm just about to head out. But will do (probably tomorrow after work).
 
Back
Top Bottom