Ahoy is an underused word these days.
Hello! I've just found your game through db.tigsource.com.
I admit, I haven't had the chance to play it yet since I'm stuck here at work, but it's installing the moment I get home.
I have a rapidly developing interest in indie and/or retro RPGs. They just seem more pure and fun than a lot of the more popular games.
I noticed that the development section of the website says you may be looking for assistance in certain areas.
I'll be happy to record any bugs I find while playing.
I'd also like to mention that I'm currently in school for programming and though my knowledge is a bit basic yet, I'd be very interested if there were some way for me to use those skills to assist you in your game development, if there is still any need. Perhaps starting with something small like minor bugfixes?
Ahoy!
Moderator: Developers
- penguinflyer2222
- Queen Penguin (Senior Member)
- Posts: 6614
- Joined: Wed Jul 23, 2008 1:51 am
- penguinflyer5234
- Sheep (Developer)
- Posts: 3025
- Joined: Wed Jul 23, 2008 1:39 am
- Location: Best Southwest
weeeeeeeeeeell
Sometimes.
C++ has a bunch of features that C doesn't, and is ONLY Object Orientated (functions classes and the like).
A lot of C+ and C code will be the same, but there is a lot of difference between them.
Sometimes.
C++ has a bunch of features that C doesn't, and is ONLY Object Orientated (functions classes and the like).
A lot of C+ and C code will be the same, but there is a lot of difference between them.
Moogirl wrote: [19:47:14] period jokes = not cool
[19:47:23] no wait it's the anus
[19:47:25] wtf
[19:47:46] a cloud cannot have that much blood
-
- {]-[0{0|307 (Developer)
- Posts: 1864
- Joined: Wed Jul 23, 2008 4:22 am
- Location: Minnesota, USA
C++ requires strict type matching
The following will compile in C
but it the calls "some_function(i)" and "some_function(k)" will create compiler errors in c++ because my_type_1 and my_type_2 are considered different types, even though they are otherwise exactly identical to "int". This seems like a pain, but is actually extremely useful for debugging.
Also, the following is illegal in c++ for the same reason
The following will compile in C
Code: Select all
typedef int my_type_1;
typedef int my_type_2;
void some_function(my_type_1 j);
void main( void )
{
int i;
my_type_1 j;
my_type_2 k;
some_function(i);
some_function(j);
some_function(k);
}
but it the calls "some_function(i)" and "some_function(k)" will create compiler errors in c++ because my_type_1 and my_type_2 are considered different types, even though they are otherwise exactly identical to "int". This seems like a pain, but is actually extremely useful for debugging.
Also, the following is illegal in c++ for the same reason
Code: Select all
void * vp = NULL;
char * cp = NULL;
int * ip = NULL;
// generates a warning because you are assigning a "const char *" object to a
// "char *" variable
char * blah = "some string";
// no problems
cp = blah;
// compiler error in c++, but not c
vp = cp;
// no error because of type cast
vp = (void *)cp;
// compiler error in c++, but not c
cp = vp;
// and so on...