 |
| Register | Login | |||||
 |
Main
| Memberlist
| Active users
| ACS
| Commons
| Calendar
| Online users Ranks | FAQ | Color Chart | Photo album | IRC Chat |
|
| | ||
|
| Register | Login | |||||
|
Main
| Memberlist
| Active users
| ACS
| Commons
| Calendar
| Online users Ranks | FAQ | Color Chart | Photo album | IRC Chat |
|
| | ||
| Acmlm's Board - I2 Archive - - Posts by Dish |
| Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 |
| User | Post | ||
Dish Spiny Level: 38 Posts: 241/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
| I found This doc. Doesn't seem to be organized very well but it covers the info okay. A rewrite of this doc couldn't hurt at all. | |||
|
Dish Spiny Level: 38 Posts: 242/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
| Bite the bullet --- get a hex editor and follow that doc I linked you before. There's not going to always be an editor to change the things you want to change. In fact... most of the time, there won't be an editor. Now is the perfect example of a time where you're going to have to get your hands dirty.... and it's under good circumstances: You know what you want to change, and there's a doc which lays it out. It'll be a good learning experience if nothing else. You'll see that using a hex editor isn't all that bad as it appears to be... you just have to actually try it ;P If you get stuck or have Qs, people on here will be more than willing to help you out... but don't expect them to do the work for you (or make an editor for you). edit - and I don't know what the deal is with everyone saying "omg smb1 music format is so horrible!". It doesn't seem to be very abstract to me. (edited by Disch on 01-22-05 11:17 AM) |
|||
|
Dish Spiny Level: 38 Posts: 243/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
Originally posted by Nebetsu Umm... why not just get the Japanese version and play it? |
|||
|
Dish Spiny Level: 38 Posts: 244/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
| Doki Doki Panic was for the Famicom Disk System... so you probably won't find it on the usual NES ROM sites. Anyway... if you've played the US version of SMB2... you're not missing much. Aside from graphical differences... the only real change is that you can't hold B to run. A few songs are different (pretty much just the Mario-themed ones... like when you go in a potion door) I think the plot was different too... like instead of it being a dream, you got sucked into a book or something. There might have been some video sequences which explained it too. But really... the actual game wasn't very different... if different at all. And actually.... the SMB2 version is way better. |
|||
|
Dish Spiny Level: 38 Posts: 245/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
| What? What would be the point of making one game into another game? Why not just play SMB2j? I suppose you could make an IPS patch which turns SMB1 into SMB2j by using SMB2j as the "hacked" rom. Or am I misunderstanding? |
|||
|
Dish Spiny Level: 38 Posts: 246/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
Originally posted by Jizuko The fact that they'd even consider making you write out code is rediculous. What the hell kind of school are you going to? What school teaches people to operate computers without actually using a computer? That's the dumbest thing I've ever heard. |
|||
|
Dish Spiny Level: 38 Posts: 247/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
Originally posted by neotransotaku That's completely stupid. I go to a freaking community college and they let you use a computer. You'd think big universities that cost a million dollars for students to attend would be better equipped than a community college that any shmuck with $100 and a diploma can attend.
If they're funded by the state... I could see the problem. But these schools charge the students an arm and a leg to attend. There should be no reason why they say "sorry, I know you paid these thousands and thousands of dollars for this semester -- but we don't have enough money to be using computers in this computer class, you have to use paper and pen instead". That's just rediculous.
So proper syntax isn't even checked? What the hell are they even teaching?
You're right. That's why they should use them
I don't see why not. If it's open book/notes... why not be able to use a computer? How does that change anything? Note: Hostility not directed towards you, I apologize in advance if I seem irritable... but I can't believe how incredibly stupid that is. Teaching Computer Science without a computer is like teaching an English class without literature -- it just doesn't work. |
|||
|
Dish Spiny Level: 38 Posts: 248/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
| I don't recall the reasons, but I started with C++ with MFC, which actually took me quite a while to get used to (MFC is sort of MS's way of making C++ more like VB -- at first it seems easier but it's actually stupid and makes things harder down the road). Anyway, I eventually broke out of the MFC nightmare and adopted more of a C/C++ mixture style. Sort of like a 'best of both worlds' setup. I avoided VB from the very beginning... since I knew I would ultimatly need to move away from it if I wanted to make anything credible (I mean really -- outside the rom hacking world, are there any respectable VB apps? Because I sure don't know of any). Anyway... my original options were VB, C++, and I think J++ (I think it was MS's attempt as doing the Java thing -- I think it flopped bigtime) --- I'm certainly glad I picked up the C++ book. The book wasn't great, but I learned the basics and picked up the rest from online sources. Took me a few years to get comfortable... but considering what little guidance I had, I think I did pretty well. I recommend everyone against using VB under ALL circumstances.... since no matter what project you have in mind, there are always easier and better alternatives. |
|||
|
Dish Spiny Level: 38 Posts: 249/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
Originally posted by HyperHacker The API is not part of C. It's part of Windows. You can't chalk that up as a downfall of the language.
Case insensitiviy is what's stupid. 'c' and 'C' are two clearly different characters and should be treated as such... not only by languages and compilers, but by EVERYTHING computer related or otherwise -- including username/passwords, webpage URLs, and preferably filenames (although Windows doesn't seem to care about case... which really bugs me). If there's no difference between cases, why bother having two cases at all? edit: disclaimer: imo XD (edited by Disch on 01-26-05 10:36 PM) |
|||
|
Dish Spiny Level: 38 Posts: 250/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
Originally posted by creaothceann They might... but they're 2 different strings. Having 2 different strings refer to the same variable is not only confusing, but sloppy. Even if the language was case insensitive it would be bad practice. And besides... case sometimes does play a major role in distinguishing between types. For example in C, I often do: HWND hWnd; "HWND" being the variable type, "hWnd" being the name of my variable (in hungarian notation... the preceeding 'h' indicates that this variable is a handle, and 'Wnd' is the name of the variable). I also often do HWAVEOUT hWaveout, HINSTANCE hInstance, MSG msg, etc.
I can't even comprehend how you figure this. How does referring to the same variable the same way all the time create misunderstandings? If anything... referring to the variable by 100 different variations of the name creates misunderstandings. Saying 'b' and 'B' should be treated as the same character by the compiler is like saying a space and an underscore should be treated the same: nonsense. Two different characters with two different purposes and two different uses. There's absolutly no reason why they should be treated the same -- they're completely different! Case matters in English when you write things. Even in your post, you had lowercase letters except where you started a sentence, where you put a capital letter. This is the syntax of English -- where capital letters and lowercase letters have different meanings. SurE yOU coUlD tYPe A SenTenCE LiKe ThIS... and yeah I would even be able to understand it -- but that's not proper English. You'll never see writing like that in a published book... or in a newspaper... or anywhere the text has been read and "edited" or comfirmed. C is no different... and should be no different. If a variable name is "MyButton"... the variable name is "MyButton". Not "mybutton" or "MYBUTTON" or "mYbuTtoN" -- those are all different. Sure you might be able to understand that they're trying to refer to the same variable (although, you can't really be sure -- like my HWND/hWnd example)... but it's no proper C. You'll never see code like that in any published program... or in any WIP source... or anywhere the code has been read and "compiled" or confirmed.
No, see... the job of the compiler is to take the code that you write and compile it. It's not supposed to guess what you're trying to say and compile an interpretted version of it. You're supposed to tell it exactly what you want. Next thing you know you'll be saying it should be doing spell check errors and that "button" and "buton" are clearly trying to reference the same variable. For heaven's sake I hope it never comes to that. If the variable name is "var"... refer to it that way. If you don't want to refer to it that way... change the variable name. |
|||
|
Dish Spiny Level: 38 Posts: 251/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
Originally posted by creaothceann I'll agree it's bad practice to have case being the sole deciding factor of different variables. Like: int Bob; int bob; That's a bad move... I'll agree. However it can have practical applications like: MSG msg; 'MSG' being the type and 'msg' being the object. However if you even don't like that -- that's understandable. I mean neither method is immune to bad coding practices. But the fact of the matter is... uppercase letters and lowercase letters are different. They are... it's not disputable. They look different... they have different contexts, and they're represented differently by the machine. There is no reason why the machine should treat 2 different characters like they're exactly the same... it just doesn't make sense.
If it really bugs you that much you could re-typdef them. But yeah... you should have to use the type as spelled by the compiler. That's only logical.
It's not guessing at all. "abc" and "ABC" are as different to the compiler as "abc" and "xyz". Upper and lowercase characters are compeltley different. Case insensitive compilers likely take your token, and instead of using it as you type it*, they convert it to lowercase before they use it so that all case is removed. * When the source of your program isn't being used 'as you type it'... the compiler is guessing what you meant to type rather than using what you actually typed ... ie: guesswork/interpretation. Like I said before... that's not the compiler's job -- it's your job to tell the compiler exactly what you want to be done. Removing case is one step away from saying underscores should be optional in token names. Like saying "this_is_a_var" is the same as "thisIsAVar". I could use all the same arguments you're using to push this type of logic. In fact... hell... let's stop putting semicolons at the end of instructions too. The compiler should be able to tell where I want my instruction to end. And you know what? When I do: int myvar; int* myptr = myvar; It should know that I mean to point to myvar... it shouldn't annoy me with silly compiling errors... it should be able to figure out what I meant to type and adjust it for me. That would "make my life easier". You can see where I'm going with this. The compiler should take what you type exactly as you type it... it shouldn't have to guess as to what it thinks you mean. Programming is an exact science... it's not guesswork. |
|||
|
Dish Spiny Level: 38 Posts: 252/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
edit -- nm... I just read the rest of your post and realized I was way offbase in what you were asking  (edited by Disch on 01-27-05 05:25 PM) (edited by Disch on 01-27-05 05:29 PM) (edited by Disch on 01-27-05 05:32 PM) |
|||
|
Dish Spiny Level: 38 Posts: 253/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
Originally posted by HyperHacker I guess I don't know VB well enough to comment here. But it seems to me that VB just front-ends a lot of the API work. There's nothing stopping you from doing that with C -- I mean you could write a library to simplify the window stuff -- although aside from actually creating the window... I really don't see what's so complicated about the API (and even window creating isn't that hard when you get the concept).
Yes but to the compiler, they're 2 completely different names. It's obvious that "btnGetFileName" and "bnGetFileName" are trying to refer to the same variable too... but they're completely different token strings. If you mean to reference the variable... type the actual variable name. It's not the compiler's job to figure what you meant to type... that's your job. The compiler doesn't write the code... you do.
What do you mean "if". You HAVE to. That's the whole point of using variable names.... it associates a token with a variable. You can't call a variable "openFile" in one part and "fileOpen" in another part... the compiler won't know what the hell you're talking about. They're 2 different tokens. "var" and "VAR" are two different strings. They're 2 different tokens. A kindergartener could see the difference.... so does a compiler. There is no reason why two different tokens should refer to the same thing --- it just doesn't hold up to logic. The compiler shouldn't "know what you mean" by something. You should tell it exactly what you mean. That's what programming is. If you don't like being specific... this is the wroooooooong area to be in.
Deal with it. If you can't reuse variable names as they're typed then you must not be a very good typist. That's like saying if I take someone else's source and I don't like their variable names... so I just use my own and expect the compiler to know what I mean by that. That's ridiculous!
MSG is a data structure, not an integer. As for HWND, HINSTANCE, etc being variable types... yeah it is kind of stupid... but typically things are typedefed with the intention that they may not be the same size on a different platform. For example, on 64-bit Windows, HWND might not be 32-bits anymore... it may be 64. If you coded something using 'long' in place of HWND, it could have a conflicting variable size. But yeah... some of the things (like WPARAM/LPARAM/HANDLE/etc) are pretty stupid... no argument here. I still use them as the context demands though. |
|||
|
Dish Spiny Level: 38 Posts: 254/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
| This is beyond my math training.. .but I've been having fun kind of thinking about it. I'm about out of time until I have to leave, so I'll spill my ideas just in case they're helpful. For any line slope... the perpendicular line's slope can be found by taking the negative reciprical. For example... a line with slope 1/2 would have a perpendicular line of slope -2. The perpendicular line would be the shortest distance between an outside point and any point on the line. So knowing 2 points on your line... you can easily find the slope... and given the slope, you can find the perpendicular slope... and given an outside point and a line slope with that point... as well as the slope of the target line.... you should be able to come up with an intersect point. I was brainstorming the formula for that but like I said I'm out of time. This would just be the 2D version... but if the logic can be found for the 2D version it could be found the same way for the 3D version. And yeah @ sqrt(x^2 + y^2 + z^2). |
|||
|
Dish Spiny Level: 38 Posts: 255/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
| Bear with me... let me see if I can explain this. Okay... let's say our line AB goes from 4,2 to 8,4... and we have another point at 6,8 of which we're trying to find the closest point on line AB. given our 2 points, the slope of line AB is 1/2. Taking the negative reciprical of that slope, we have a slope of -2/1 for our perpendicular line CD's slope. From here, I tried to find the point on line AB which had the same X coord as our point C (6,8). Using the slope of 1/2 and either point... we can find that 6,3 is a point on line AB. Now our point at 6,3 and our point at 6,8 will gradually be moving closer together at fixed slopes. To find out where they intesect, we only need to find how far the line will move in the X direction... because both lines will be moving a total of 5 in the Y direction (6,8 and 6,3 are only 5 units apart on the Y). Here, we take the ratio of absolute Y movement in each slope... line CD (slope of -2) will be moving 2 units for every 1/2 unit moved by line AB. So the ratio would be 2:0.5.. or 4:1 Knowing this ratio, we only need to find the point on CD where the Y has moved 4/5ths of distance to our "equal X point" (line CD had point 6,8 and line AB had point 6,3... so the distance was 5) 4/5ths of 5 is 4... so from point 6,8... we need to find the point which is moved down the Y axis by 4 units... 8-4 is 4... so that'd be ?,4... and that's where lines AB and CD intersect. Given the slope of line CD being -2/1... we can find that point to be 8,4... which is the nearest intersecting point! Given that 2D method... the process could be repeated for a 3D method. Once you find the nearest point on the X / Y plane... you just need to find the point on the XY / Z plane. I hope that made sense... because I have to leave for school like now. XD edit - clarification error corrected (I really gotta go!!!) (edited by Disch on 01-27-05 07:28 PM) |
|||
|
Dish Spiny Level: 38 Posts: 256/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
Originally posted by creaothceann The thing is... it's not philosophy... it's fact. Uppercase and lowercase are two different things. A preschooler can look at 'A' and 'a' and tell you the difference. By your logic... if you told the machine to output "A sentence like this." and it outputted "A sEnTANce LiKE tHiS."... there would be nothing wrong with the compiler... since the output it outputted was the "same" as you told it to output. Well I don't see how you could possibly think that... because the two are obviously different. Personally... if the compiler I was using did that, I'd throw it out. |
|||
|
Dish Spiny Level: 38 Posts: 257/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
Originally posted by HyperHacker So because you can't remember the variable/function names use by some other coder... you should be able to put in whatever names you want? That doesn't make any sense. I don't like how this guy named his variable "accumulator"... so from now on when I use his source... I'm just going to refer to it as "A" -- and the compiler should know what I mean. <-- that's basically what you're saying. Even if you do slip up with your typing and type the wrong variable name. So what? The compiler gives you an error.. .and you go correct it. But it's not that hard to just remember a freaking variable name. You're way overexaggerating the difficulty. I've used other people's libraries and bits of other people's source in my programs before... it's not hard to the functions/vars as they're named. And if it really is that hard for you (which I wouldn't believe for a second), you could do that #define thing Para mentioned.
bah... I used to type "sentance" all the time... I had to make a real effort to remember to type "sentence"... guess that one slipped through  Anyway... that aside. How would you like if it all the text your program outputted was in random cases? Or all uppercase? Or all lowercase? It would suck, right? That's because case is different. 'H' is not 'h'... they're two different characters. (edited by Disch on 01-30-05 02:32 AM) |
|||
|
Dish Spiny Level: 38 Posts: 258/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
| It's bad because it's confusing. It's like someone saying "FF2" when they mean the FF2 portion of DoS. Sure on some level it's right... but it's silly. FF3j or FF3us is more specific. But without the country suffix, it's assumed (by most people in the rom-hacking world) to be the original, first FF3: FF3j. |
|||
|
Dish Spiny Level: 38 Posts: 259/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
Originally posted by dan And the term "hacking" has a different meaning to those normal people too... but in the emulation and rom-hacking worlds, terms get used a little differently. Most people take FF3 to mean FF3j, since that was the original FF3. |
|||
|
Dish Spiny Level: 38 Posts: 260/596 EXP: 355646 For next: 14801 Since: 03-15-04 From: Disch Since last post: 18 days Last activity: 18 days |
| ||
Originally posted by HyperHacker It's the exact same principle.
BECAUSE THAT'S THE NAME OF THE VARIABLE. You can't just start referring to the variables by tokens which aren't their name. It makes no sense. Yes that's a stupid name for a variable... so is "asjflasdflmlaksdmf"... but I can't just start using "stupidvar" in place of "asjflasdflmlaksdmf" just because I can't remember how to spell "asjflasdflmlaksdmf". if "asjflasdflmlaksdmf" is the variable name, that's what you have to refer to it as.
My point is that while you'd agree that "This is a sentence" and "THiS iS a SeNtEnCE" are two completely different strings -- you still insist that "somevar" and "SomeVar" are the same string. That's the hole in your logic.
Nothing will blow up if I refer to "var1" as "var_one" either... but it makes no sense to do that. They're two completely different tokens. Treating two tokens like they're the same makes no sense. Originally posted by Squash Monster Any competent English Major... or even anyone know knows anything about English will tell you that uppercase and lowercase letters cannot be interchanged freely in [proper] English. They both have contexts where they're both supposed to be used. This pretty much means they're 2 different things (if they're the same, there wouldn't be any rules restricting the use of one in certain situations). --- hell, if they were the same thing we wouldn't be able to type both of them into the keyboard. While "A" and "a" may represent the first letter of the alphabet [in two different cases] that doesn't make them the same thing. "2" and "two" also represent the 2nd number in our numbering system and are even interchangable whereas 'a' and 'A' are not... but I don't think anyone here would consider "2" and "two" the same thing. I'll just chalk this up to another stupid VB-spawned problem. VB teaches these back-asswards rules that defy all logic and make no sense whatsoever... only to make the programmer have to completely forget all those stupid rules if he/she wants to move to pretty much any other programming language in existence (and make no mistake... all the good ones are case sensitive -- for obvious reasons). I guess it's just another reason why VB is wretched -- especially to start with.  (edited by Disch on 02-01-05 03:46 AM) |
| Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 |
| Acmlm's Board - I2 Archive - - Posts by Dish |
