Shadowdancer

Member
  • Content count

    687
  • Joined

  • Last visited

Community Reputation

319 Neutral

About Shadowdancer

  • Rank
    Advanced Member

Personal Information

  1. A Daft Statement

    http://youtu.be/5hfYJsQAhl0   'nuff said.
  2. Starting to hate Google...

    [quote name='Sirisian' timestamp='1320181677' post='4879386'] Javascript needs to be replaced. I along with others online have mentioned this for a long long time.[/quote] I'm quite new to JS, but from what I've seen, the language itself is "fine" (plus or minus personal preferences or offbeat requirements). What needs to be replaced is its integration in browsers, mostly [list=1] [*]The overly shitty execution model that allows for "fun" things like just executing stuff by appending it to the document, and [*]The supremely half-assed brainless DOM API that just does some things wrong (ever tried using an onclick handler on a submit button?) and is generally decoupled from what the DOM is really looking and acting like. [/list] Both are not language-, but integration issues.
  3. Wiring a house for Ethernet

    [quote name='AndreTheGiant' timestamp='1298827695' post='4779720'] Not 100% sure what you mean by SOCKET... and I'm even less sure what an LSA SOCKET is. I gooogled it but wasnt to confident with the results. Can you explain a little bit?[/quote] A socket in this context is what you plug a cable into. LSA is a type of wire connector that's basically a row of pressure contacts that you put the wires in and push it into position and cut it off with a special tool, so you don't need to strip individual leads. It's standard for that kind of wiring. Works like that: [url="http://www.youtube.com/watch?v=sHy8mtW9eak"]http://www.youtube.c...h?v=sHy8mtW9eak[/url]
  4. Wiring a house for Ethernet

    Ethernet cabling in the post-10Mb/s world is a one-cable-per-socket thing. You could technically still run two 100Mbit links over a single Cat6 or Cat7 cable, but that requires luck and forbids gigabit ethernet. Don't use powerline, that stuff is retarded. If you need to hack around a connectivity shortage, use WLAN. If that doesn't work, use a power drill. IME, most rooms will be fine with two sockets, so you run two cables there. Have 4 or even 6 sockets in rooms used as home office (PC, laptop, network printer(s), …) and where you park your entertainment electronics (networked TV, game consoles, but that stuff will be fine when you run it all over a single switch). If you're using wired phones, reserve a cable for those; the 4- and 6-wire modular plugs on phone cables fit in RJ45 sockets. On cables: Cat6 is fine and should be completely sufficient too, Cat7 is overkill in home installations that aren't neighbouring an aluminium melter. It's already fairly unwieldy since it has lots of shielding, but since you are building the walls around it, that shouldn't be an issue. You can also run GE over Cat5 links with some luck, and chances with Cat5e are really good. TL;DR: Get Cat6, if you can't fit that into some hole, use Cat5e there. On sockets: GET LSA SOCKETS! This cannot be stressed enough. I had the joy of installing sockets where the cable contacts were screw terminals. After wiring one or two of those, Cthulhu sounds like a nice guy. Make sure they're Cat6. On tools: You need an LSA tool with integrated cutter, and an insulation stripper for multi-lead cables. You can theoretically get away without those, but believe me, you want them.
  5. Language Builder IDE

    Technical aspects aside, "Colorizing"? Wouldn't "Colors" do it? ;-)
  6. Underwater scenes

    Use caustics sparingly, they are mostly a shallow water effect that gets lost with depth very quickly. A lot of ambience under water is from the very specific light filtering, as well as floating particles and audio.
  7. The Downward Spiral

    I totally agree with you Mike
  8. 48 Hours Later - Moving Forward

    The ads smacked inside the forum thread view need to go. It's not quite as bad as allowing "posting ad bots" on the forum, but it's still untenable that advertising content gets mixed inside (more or less) contiguous user-generated content.<br>
  9. Pacman Collision Detection With Sides Of Maze

    [quote name='flodywan' timestamp='1294714448' post='4757027'] Doesn't this mean that pacman would have to be the same size as all the other tiles?[/quote] As the article states, the sprites can be bigger than the "tiles"; however, the only thing that counts for collision is the centre point of the sprites. Animation is smooth. One approach would be to limit movement so that the centre point of an actor cannot move beyond the centre of a tile if the tile beyond it (along the path of the actor) is a wall.
  10. Segmentation Fault

    The situation on Mac seems to be a bit of a charlie foxtrot, since it traditionally used colons as separators. If you are just targeting OSX, use slashes (it's U**x based). Make sure you do not use slashes or colons inside path elements, since things get interesting then.
  11. Segmentation Fault

    Windows understands slashes as path separators just fine. You can also use boost::filesystem::path in C++.
  12. Pacman Collision Detection With Sides Of Maze

    [font="Comic Sans MS"][size="5"][color="#ff00ff"]You want to read [url="http://gameinternals.com/post/2072558330/understanding-pac-man-ghost-behavior"]http://gameinternals...-ghost-behavior[/url][/color][/size][/font]
  13. Vacation over, back in office, looking forward to once more work with one of the ugliest development frameworks on earth.
  14. Updating an old web framework to use new support libraries is fun.
  15. GCC 4.4.5 without optimisation: Source, a bit greebly to keep the compiler from optimising out everything (just initialising to 0 and then incrementing had the compiler just assign 1 at -O2): #include <stdio.h> #include <stdlib.h> int main(int argc, char** argv) { int i, j; if(argc < 2) { i = j = 0; } else { i = j = atoi(argv[1]); } ++i; j++; printf("%d, %d\n", i, j); exit(0); } Assembly generated by "gcc -Wall --std=c99 -S" with added comments: .file "prepost.c" .section .rodata .LC0: .string "%d, %d\n" .text .globl main .type main, @function main: .LFB0: .cfi_startproc pushq %rbp .cfi_def_cfa_offset 16 movq %rsp, %rbp .cfi_offset 6, -16 .cfi_def_cfa_register 6 subq $32, %rsp movl %edi, -20(%rbp) movq %rsi, -32(%rbp) cmpl $1, -20(%rbp) jg .L2 movl $0, -4(%rbp) movl -4(%rbp), %eax movl %eax, -8(%rbp) jmp .L3 .L2: movq -32(%rbp), %rax addq $8, %rax movq (%rax), %rax movq %rax, %rdi call atoi movl %eax, -4(%rbp) movl -4(%rbp), %eax movl %eax, -8(%rbp) .L3: addl $1, -8(%rbp) ; first increment addl $1, -4(%rbp) ; second increment movl $.LC0, %eax ; start printf call movl -4(%rbp), %edx movl -8(%rbp), %ecx movl %ecx, %esi movq %rax, %rdi movl $0, %eax call printf movl $0, %edi call exit .cfi_endproc .LFE0: .size main, .-main .ident "GCC: (Debian 4.4.5-10) 4.4.5" .section .note.GNU-stack,"",@progbits If you can explain why the first addl would be inherently faster or slower than the second addl, you win.