next »

[Geti]

Almost surprisingly, not that I've seen yet. Apparently angles being accurate and a few other issues was unimportant for anything immediately visible. We'll see if something breaks in a month

stuffing around with win32 all day to "quickly make a simple and minimal launcher for moonman". big mistake.

Heh, aw. GUI stuff is so easy to waste time on :/

[Klaim]

Memory leaks. Memory leaks everywhere.

C/C++?

You can memory leak with almost any language.

Yeah, but much more easily with C/C++. Avoiding memory leaks in C(++) is a trained skill in itself

If you don't program in C in a C++ program, no memory leak.
The problem is more that when you learn it most of the time you learn to manipulate pointers, which is the source of memory leaks. While if you learn it properly at the beginning, not using pointers util you have to, then no memory leaks appear. Like, I didn't have any for years once I learnt that I learnt it totally wrong. Now as soon as I see new and delete in a source code, I'm getting suspicious.

[_Tommo_]

If you don't program in C in a C++ program, no memory leak.
The problem is more that when you learn it most of the time you learn to manipulate pointers, which is the source of memory leaks. While if you learn it properly at the beginning, not using pointers util you have to, then no memory leaks appear. Like, I didn't have any for years once I learnt that I learnt it totally wrong. Now as soon as I see new and delete in a source code, I'm getting suspicious.

this.
And Get() - Release() reference pointer style is even worse because it attempts to solve the problem but actually makes it worse (you still have to remember to Release(), but not once - EACH time you Get() something!).

[rivon]

I just program something, then run Valgrind on it and fix the leaks. Rinse and repeat

[Klaim]

I just program something, then run Valgrind on it and fix the leaks. Rinse and repeat

I actually do something like this (but on Windows so no valgrind) which is why I say I didn't have leaks for years. Only on long projects thought. I even sometime write leaks to make sure it's not the tool that don't work anymore for some reasons.

(actually there are leaks sometimes, mostly due to libraries not releasing automatically their resources, like protobuf, so you have to do it explicitely by calling some functions if you think it's necessary - I do because otherwise I can't catch mine)

[Gregg Williams]

I just write code where allocation and deletion is usually 100% contained to some sort of level initialization/cleanup.  Don't remember the last time I had a real memory leak.

[epcc]

I'm creating all game objects with new and they are automatically added to level object list.
to delete them, I set a field called mustdelete to true and at the end of every frame the level object removes them from the list and deletes them. All other objects are either created on stack or created only once, at game start. Haven't had memory leaks with game objects since.


Now I'm rewriting level format and already having doubts.
There's going to be maybe 20 functions that look almost the same, the only difference is the object name and sometimes an extra parameter.
Is there some better solution than that?

Code:

static int con_LuaObject(lua_State* L)
{
    TBasicInfo basicinfo;

    TLuaObject* ptr=new TLuaObject(basicinfo.pos,basicinfo.angle,basicinfo.type);
    CON_END
}

All these functions go to a lua list, so every object calls the correct constructor with correct arguments according to their type.
CON_END expands to

Code:

#define CON_END ptr->color=basicinfo.col;\
InitObjectName(L,ptr);\
ptr->GetLuaObject(L);\
return 1;

[Schrompf]

Make it a template. You'll still need to register all instances of this template function separately with LUA, but at least you only have to write it once.

[epcc]

The problem is, that some objects need additional parameters. For example:

Code:

static int con_Door(lua_State* L)
{
    TBasicInfo basicinfo;

    int frame=li_GetTableInt("frame"); <- this one right here, for example.
    TDoor* ptr=new TDoor(basicinfo.pos,basicinfo.angle,frame);
    CON_END
}

This makes any templating hard.

[eigenbom]

@epcc write a simple code generator?

[BorisTheBrave]

imho it's not wise to use C++ inheritance when you are binding to Lua - why not handle that sort of logic in Lua, where it is easier and more flexible.

Anwyay, given what you've got, use SWIG to quickly generate bindings from C++ to Lua - half the time all SWIG needs is the header file, and it does the rest.

[epcc]

SWIG is just what I need. I should have used it from the start, instead of manually writing my own.
It's hard to estimate if the work will eventually get mechanical enough that it could be done by a computr

[eclectocrat]

Plugging my own tutorial, look in the TUTORIAL sections on here, I wrote a system that will handle most LUA-C++ things transparently with no additional runtime cost. It's really quite easy once you wrap a few things in templates and MACROS. Yums.

[Fallsburg]

Perhaps this should go in the Happy Programmer thread since I fixed my problem, but I'm still more grumpy than happy.

Apparently, in Unity using the XMLDocument class works perfectly fine with DTD when in the editor, but .NET throw a NotImplementedException when it is actually built.  Instead of changing all of my xml parsing to use a format that ignores DTD (since the supposed ways to make XMLDocument ignore DTD don't work), I just removed the DTD from the xml file. 

[Belimoth]

I have gotten no work done in the last two days because I can not get anything to render.
I can get things to render if I comment out the creation of any entities:
Here is the code for the entity class:

Code:

Class MyEntity Extends AbuEntity
	Field x:Int, y:Int
End

IT DOESN'T EVEN DO ANYTHING

[Muz]

Merging new code into some other new code.

sometimes programming with two people is slower than one person doing it alone. Only 33 out of 43 left to do...

[skew]

writing php the whole week... while thinking about how much better the code would be in python 

[Eendhoorn]

I absolutely hate the unity asset store. I always loved how generous and helpful programming communities are to each other. If I have an issue, or just don't want to reinvent the wheel with XNA or any other framework, I could search and find someone who would be generous enough to share his framework/solution for free.

But every-goddamn-thing is paid in the unity asset store. And it's pretty damn expensive aswell. A simple 2D tilegrid plugin costs $50.

[Geti]

writing php the whole week... while thinking about how much better the code would be in python 

Why did you have to do it in PHP?

[sublinimal]

C++ woes. A template function didn't compile, so I was told to move it into the header... which revealed some circular dependency issues... that only got worse as I started fixing them.