Posted: Tue 16 May, 2006 4:34 pm
Well that explains it better, and I did read the read me!!
So have you updated it since last time?
So have you updated it since last time?
for your 1 bit pleasure!
https://maxcoderz.org/forum/
Yup. Nearly no overhead still is some overhead, plus more complex (to write, to maintain, to port) code, plus more bytes of code for something that you'll never ever need.kerm_martian wrote:But that's my point - there's nearly no extra overhead for the infinite possibilities. I assume 254 because FF or 00 is used for all-net addressing?
Well that's very ambitious, but I prefer a small, fast, easy to code/maintain/port, graceful breakdown (quit with error message or just quit, or jump to program specific error handler if present, don't know yet) over hundreds of bytes of error checking and wasted clockcycles in calculating checksums and whatnot for -again- something that hardly ever happens. By the way; you can never anticipate bad programming. People will always find ways to crash even the most stable bit of software...I'm trying to anticipate as many problems as possible: bad programming, random disconnection, lots of noise, calculator crashes sending random stuff to the linkport, etc.
I guessed you would. It's a nice way to handle things, I'll admit that, but I think we just have very different goals in mind for this. You're trying to recreate the Internet with all it's inpredictabilities, I'm just trying to make a nice and easy to use package for people to make multiplayer games and stuff with. My code is clear, layered, documented, meant to be read. My routines do their job and nothing more. Yours will -I expect- be something external (embedded in Doors CS right..?) that you communicate with through buffers and by calling routines, and you are afraid you'll limit people so you try to put everything in it that anyone could ever need. Where in my setup people can just expand on my routines themselves.As a matter of fact, I have a flag that gets reset by the interrupt when the frame goes through and is acknowledged by the receiver, so you know _exactly_ where it's at.