|
Thread Rules
1. This is not a "do my homework for me" thread. If you have specific questions, ask, but don't post an assignment or homework problem and expect an exact solution.
2. No recruiting for your cockamamie projects (you won't replace facebook with 3 dudes you found on the internet and $20)
3. If you can't articulate why a language is bad, don't start slinging shit about it. Just remember that nothing is worse than making CSS IE6 compatible.
4. Use [code] tags to format code blocks. |
On May 05 2015 01:32 Artesimo wrote:
When using list/multilinked lists, should I rather make a class that holds the beginning of the list or should I rather keep the first element of the list as an empty element onyl to find the list? I found both ways used, but the last one seemed odd, but maybe there is some performance-benefit.
Also, when it is practical to group the list elements in some sort (like a dictionary with A,B...), should I create a list for each group, or should I rather use one big list, and have pointer to certain elements stored elsewehere, that simly point to certain locations(like "words with C start here"->)? If I want to use one big list, it seem like having a class that holds this information is best.
To answer your first question in a very simple way: If your list looks something like...
class ListElement
{
...
ListElement *next;
SomeType data;
};
...you really just need a ListElement* to be able to access the first element.
That's not an empty element, it is actually the first element. The list exists implicitly as these elements are linked together with the "next" pointers.
|
On May 05 2015 01:32 Artesimo wrote:
When using list/multilinked lists, should I rather make a class that holds the beginning of the list or should I rather keep the first element of the list as an empty element onyl to find the list? I found both ways used, but the last one seemed odd, but maybe there is some performance-benefit.
The head of the list being a blank makes it easier (implementation wise) to do insertions and things at the start of the list. You need special cases if that position is data.
In terms of performance the difference should be negligible.
|
Thanks, another question:
I found out that c++ also features <list> which seems to do pretty much everything I did by hand. Is there any benefit to not using <list> for a linked list rather than understanding it better buy having build it by hand before?
|
I think anyone would recommend, implementing it yourself first to understand it better.
|
|
|
You can implement it yourself to understand it better, but you should use the standard library implementation anyways. It's most likely more optimized and of course most certainly bug-free.
|
On May 05 2015 02:35 Blitzkrieg0 wrote:
The head of the list being a blank makes it easier to do insertions and things at the start of the list. You need special cases if that position is data.
I was assuming educational purposes when I answered. In what real-life scenario would you consider using your own implementation and hiding the "special cases" behind a blank first element feasible?
If just using a list was the issue then the obvious answer should be using stl or boost implementations.
|
On May 05 2015 08:11 Khalum wrote:Show nested quote +On May 05 2015 02:35 Blitzkrieg0 wrote:
The head of the list being a blank makes it easier to do insertions and things at the start of the list. You need special cases if that position is data. I was assuming educational purposes when I answered.
I was too which is why I told him why you would write the code with blank elements.
|
It's important to know how the list structure actually works in case you ever need to design or implement a data structure similar to it, and so that you use the list itself efficiently. Lists are important foundations for lots of other abstract data structures since they are so basic. To understand a stack or a queue you need to understand lists, and since lists are basic, they can help you understand things like trees too.
To answer your first question, if you are making a list to store strings, I recommend implementation of a trie (where each node is a character, boolean for if the node and its ancestors constitute a word, and an array of 26 pointers) if you have some extra time to code it. If you generally want to store related data in a list-like structure you could make a list of lists.
|
On May 03 2015 12:08 Nesserev wrote:Show nested quote +On May 03 2015 11:25 Nausea wrote:
I'm a noob and thinking of trying to put together a bejeweled game to learn from. (In c++)
I just thought I might ask here what container i may want to use for the jewels, since I guess I will have to remove and move and add stuff very often.
I think most people tend to go for a 2-dimensional std::vector/array, or perhaps even a map with pairs as keys. Personally, after having dealt with 'quadrants'(?) far too many times, I think the best option (clean, flexible, most optimal) would be writing your own class that provides all your needs, around a one dimensional std::vector< ... >. It makes iterating rows/columns very easy and clean, and you can just use pointer/iterator arithmetics. Note that the only case that it's not very good at, is expanding the quadrant in both dimensions. (EDIT: Then you should prefer a 2D vector.) Show nested quote +On May 03 2015 08:20 Blisse wrote:
From my experience, should be documenting code while you write it before you have and before you complete code reviews. Code + technical design documents should be enough to explain why the code exists the way that it does. Never really saw the point in excessive documentation except for very important files (because that way when I see a file with a couple long paragraphs at the top I know that it's important).
What are you documenting that takes so long? I never skip the inline comments, which help a lot during the coding process itself, or organizing/chaptering the code, but when I just want to continue coding, I postpone writing the class and method descriptions, code examples, etc. until later. I guess I might be a little bit guilty of excessive documentation. It's not like I document the most menial of details, but I tend to write documentation for the user of the classes, and developer/maintenance separately; and when I do, I pretend that the other person is a 5 year old. I don't think that it's a lot of documentation, it's just that I tend to get annoyed with it really fast. If only documentation was as fun as coding, or well... you could say it's part of coding, just the boring part :S
In my opinion, I think your usage of the code should generally be enough of an example of *how* to use it. Exceptional circumstances of the call of the code should be documented of course, and it depends really on what the code does, but you *really* shouldn't have code paths that are *never* executed when you put the code up for code review/commit, so your usage of the code should document all the possible usages. So the usage of the code should generally be documented by the code itself. Again, with additional *function* level comments to document exceptional/complicated/contextual parts. If the structure of "why" something happens isn't clear, there may be a clearer way to implement it... if not then really you really need the comments, but I don't think that should happen that often during the coding practice.
Actually not a super fan of descriptive function names unless that function is actually used more than once now, a bit of a change from before.
It's a bit harder to explain developer/maintenance separately. I think the normal practice is to message/include the owner of the code previously during the code review and before starting to change the code, or coding in pairs, or similar, but I agree a good idea is explaining the reason for any non-obvious design choices.
|
How important is it to have a personal website if you are planning on going into software (not necessarily web) development? I'm thinking about making one so that I can have a place to talk about/link/host my projects, show off/practice web dev skills, and put up a brief resume. It would be cool to have an email address @ my name too, I imagine
|
On May 08 2015 03:51 Chocolate wrote:
How important is it to have a personal website if you are planning on going into software (not necessarily web) development? I'm thinking about making one so that I can have a place to talk about/link/host my projects, show off/practice web dev skills, and put up a brief resume. It would be cool to have an email address @ my name too, I imagine
I made one. It's usually quite cheap/free to run and can just act as a sort of hub for career stuff. I kept my site quite simple. It has my resume, a small "about me" section, a simple blog that I basically never use (I threw it together quickly in Django just to see how Django worked), and a page that details a couple of projects I've done. Nothing fancy.
But yeah, I mostly use my domain so that I have an email that isn't a gmail or thing like that.
|
Hey for anyone that is familiar with CS undergrad classes (most people here probably), how bad of an idea would it be to take these classes at the same time, assuming like 15-20 hours working also? Just in terms of time required in general. 16 week semester.
Object Oriented Programming and Design (major core class, like a mid level thing)
Systems Programming and Unix (same as above)
Introduction to Discrete Structures
Calc 2
I was sort of thinking I might need to drop one. These seem like they all might be classes that take up 15-20hrs/week but I'm not sure.
|
It's not "important" but it's a nice thing to have that just shows potential employers you're a bit more than averagely interested in technology. Plus having your own domain email is nice.
I do it to blog and because web design is fun.
|
On May 08 2015 06:43 GwSC wrote:
Hey for anyone that is familiar with CS undergrad classes (most people here probably), how bad of an idea would it be to take these classes at the same time, assuming like 15-20 hours working also? Just in terms of time required in general. 16 week semester.
Object Oriented Programming and Design (major core class, like a mid level thing)
Systems Programming and Unix (same as above)
Introduction to Discrete Structures
Calc 2
I was sort of thinking I might need to drop one. These seem like they all might be classes that take up 15-20hrs/week but I'm not sure.
You should talk to some students at whatever university you are attending. If all three of those classes involve a lot of coding then you probably don't want to take them at the same time, but a student who has taken them would know much better than people on the internet.
|
On May 08 2015 06:43 GwSC wrote:
Hey for anyone that is familiar with CS undergrad classes (most people here probably), how bad of an idea would it be to take these classes at the same time, assuming like 15-20 hours working also? Just in terms of time required in general. 16 week semester.
Object Oriented Programming and Design (major core class, like a mid level thing)
Systems Programming and Unix (same as above)
Introduction to Discrete Structures
Calc 2
I was sort of thinking I might need to drop one. These seem like they all might be classes that take up 15-20hrs/week but I'm not sure.
Find out everything you can about the professors. Find out how intense the coursework is. Find out how many hours a week you will actually need to commit to doing well in the class. If you OO class is anything like mine was, it shouldn't be too bad. Just don't put things off and you'll be fine.
I did two terms (one this year, one last) of 4 CS classes per term. It's definitely possible to do so, but again it depends entirely on the prof. My Operating Systems class had more homework than 2-3 other CS classes combined while some of my more theoretical CS classes I could get away with simply doing the readings an hour before class and then committing an evening or two to the homework every couple weeks and do just fine in them. It all depends on the professor and the amount of work they want you to do.
You need to find out specifics. If one of those classes is a pushover then yeah, you can probably take all 4. If all 4 require a lot of work, then it might be wise to take only 3 or else your average could take a big hit.
|
On May 08 2015 07:13 Blitzkrieg0 wrote:Show nested quote +On May 08 2015 06:43 GwSC wrote:
Hey for anyone that is familiar with CS undergrad classes (most people here probably), how bad of an idea would it be to take these classes at the same time, assuming like 15-20 hours working also? Just in terms of time required in general. 16 week semester.
Object Oriented Programming and Design (major core class, like a mid level thing)
Systems Programming and Unix (same as above)
Introduction to Discrete Structures
Calc 2
I was sort of thinking I might need to drop one. These seem like they all might be classes that take up 15-20hrs/week but I'm not sure. You should talk to some students at whatever university you are attending. If all three of those classes involve a lot of coding then you probably don't want to take them at the same time, but a student who has taken them would know much better than people on the internet.
That doesn't seem so bad because it's just four classes. I don't think OO is very bad at all (in terms of difficulty of understanding, of course your professor could assign a ton of work) and discrete, at least where I go, has a reputation for being easy. Calculus II has a reputation that I think is unwarranted; its difficulty is mostly dependent on your preparedness and ability with math. Can't speak to your Unix course
I'm going to echo what others said and tell you that you should ask former students and look online to see how muck work they are.
Doesn't seem so bad, but then again I don't work 15-20 hr per week. If you aren't accustomed to going out on weekdays it seems manageable.
|
Zurich15365 Posts
Wanted to deploy a small app on Google Cloud Platform. Can anyone confirm it's not available for individuals in Europe/EU? (only for business)
|
What part of Google Cloud Platform?
|
Zurich15365 Posts
On May 09 2015 12:50 phar wrote:
What part of Google Cloud Platform?
As far as I can tell, any, but app engine in my case.
|
|
|
|
|
|
EPT
