Thanks for that information, I will certainly study it.
Currently I let my user set their language.
And when I perform something similar to send_to_char( ),
I have the code here
// htam: print bilingual language formatted
void CH::bprintf( const char *eformat, const char *cformat, ... )
{
char buf[LEN_STRING];
va_list marker;
va_start( marker, cformat );
if( language == L_CHINESE )
vsprintf( buf, cformat, marker );
else
vsprintf( buf, eformat, marker );
va_end( marker );
if( buf[0] != '\0' )
desc->write_buffered( buf, 0 );
}
You can see that I need to make the check every single bprintf()'s, for
performance, is this better or is making two muds using shared memory
better?
I only ask this as a SIDE question, my main reason for splitting is for
maintainability. For I might actually give my schoolmates a English only mud
to play (I mean play with the code, not the game), since they dislike having
to read a program with a lot of wierd characters (their computer can't read
Chinese), so if I have a seperate mud, I would only need to disallow shared
memory and on they go. Currently, I have more then 500 bprintf()'s (ya, I am
still developing, so not that many yet), if they were to edit every single
one and remove the unknown characters, it would take some time. :]
Of course, I am not totally set about what I will end up doing, this whole
project is just for my own practice and entertainment.
Htam
----- Original Message -----
From: "Jason Gauthier" <[EMAIL PROTECTED]>
To: "Dale Kingston" <[EMAIL PROTECTED]>; "Jed Yang" <[EMAIL PROTECTED]>;
<[email protected]>
Sent: Tuesday, September 09, 2003 10:21 AM
Subject: RE: Snippet/Walkthrough for making a mud listen on multiple ports .
> >
> > Their not going to beable to share memory, So what your going
> > to have to do, is have the one connect to the other, and pass
> > the information back and forth between each other.
>
> Why are they not going to be able to share memory?
> http://www.newriders.com/books/opl/ebooks/0735710430.html
>
> Read up on Interprocess Communications. Specifically "shared memory"
>
> (Jed- this is a really great manual, BTW)
>
>
> > Where as I mentioned this before, it would be much wiser if
> > you used 1 program, and 2 ports. And then you just throw in
> > some code to have it seperate the people.... Or you could
> > take it a step farther, make two linked lists for
> > descriptors, and two linked lists for char's. And then run
> > through the mud that way.
>
> Wiser to you, but if taken in the original context of his request, it's
not.
> He wants an english mud, and a chinese mud.
> Two different muds, preferably using the same in-game information.
>
> > Two programs sharing data, I think is a little more
> > complicated then a High Schooler is probably willing to sit
> > through and do.... And it's alot of extra work, when you can
> > get 1 program that does the exact same thing, much easier.
>
> I don't think so.
> Shared memory is not hard once understood, and there are many resources
out
> there that demonstrate it.
>
