Newcomer

[Tomaaz]

I've posted 25 posts and I'm still a newcomer, while Peter who's posted 5 and Aurel who's posted none are regular members. Och, I see... Cybermonkey is a newcomer, too, so it must be the highest position here!

[Cybermonkey]

Yeah, I've got some problems with groups and group membership with the new software. I hope I can fix it soon ... 

[Aurel]

I've posted 25 posts and I'm still a newcomer, while Peter who's posted 5 and Aurel who's posted none

Tomaaz ..
Is this really important to you ?
This is such a trivial 'nick' and is not important for me at all...
I don't have made any post in first place because i am not very much interested
for game programming..

All in all,this forum now looks quite well...

[Cybermonkey]

No problem: after 50 posts you are a Jr. member.  (me too, of course - I can't change the status of that; admin is not god ...   )

[Tomaaz]

No Aurel, it's not important for me. I would rather say it's funny. But, if we agree it's not important, it's better to remove it completely instead of having it like it is now (meaningless and confusing). Just my opinion.

At the moment I'm also not interested in making games and I really believe I will be ban from this forum for starting topics not related to games.

BTW How is AurelBasic? Did you fix memory leaks? Does it support object oriented programming, yet? Or did you give up it and decided to contribute to ScriptBasic? Hey, do you know this - the simplest GUI example in Python?

Code: [Select]

from easygui import *
msgbox("Hey Aurel!")

[remember that this is just offtopic. ]

[Aurel]

Hey..i know that this is offtopic.
I use few tools to detect memory leaks,but is not directly produced by Aurel Basic then
with language in which is developed...grrrr
Infact i think that something smell very bad in garbage colector...
ABasic is in 'status quo' , work on something different then basic -like using oxygen.
syntax will looks like this:

Code: [Select]

def $1,$2,$3,$4,$5,$6
wForm  0, 0, 400, 300, #MMS,0, 'New Caption!'
doLoop number, start, end
wText xPos , yPos , $text
This is still just a experiment.

[Tomaaz]

I use few tools to detect memory leaks,but is not directly produced by Aurel Basic then
with language in which is developed...grrrr

This is the "advantage" of writing in not popular languages. And two years ago you were singing songs about how great Creative/Emergence BASICs are...

ABasic is in 'status quo' , work on something different then basic -like using oxygen.
syntax will looks like this:

Code: [Select]

def $1,$2,$3,$4,$5,$6
wForm  0, 0, 400, 300, #MMS,0, 'New Caption!'
doLoop number, start, end
wText xPos , yPos , $text
This is still just a experiment.

Just for curiosity - what's the point of it? Are you writing it because you just want to or do you believe that there are potential users of it?

[Aurel]

This is the "advantage" of writing in not popular languages. And two years ago you were singing songs about how great Creative/Emergence BASICs are...

heh...
You shot again in wrong direction.
Creative Basic & Emergence Basic are still very well created languages.
I don't know do you understand problem properly.
EBasic is compiler who compile source code to asemmbler source (NASM) which play main
role in complete process for creating final exe file,ok...
So i can't blame author if something is not optimized or slow or have mem leaks.
I can susspect only in EB header which have ( it looks to me ) problem with Heap Memory .
So even i don't like to much author of CB/EB i can tell you or anyone else
that EB is still one of very good basic compiler ever written for Windows.

Just for curiosity - what's the point of it? Are you writing it because you just want to or do you believe that there are potential users of it?

Yes i just want to do this because i like this stuff.

...potential users...

This new thing will be open source and i really don't think about potential users.

[Tomaaz]

You shot again in wrong direction.

Aurel... These are your words:

I use few tools to detect memory leaks,but is not directly produced by Aurel Basic then
with language in which is developed...grrrr

So, in what language is AurelBasic developed? Or maybe you're trying to tell me that something wrong is with NASM?

[Aurel]

ABasic is developed in EBasic, but final executable is produced by NASM.
EBasic is not direct machine code compiler.
Pure Basic use FASM for example.
FreeBasic use GAS( i think)
For a difference Oxygen Basic have your own o2 assembler, or in bettter way
Oxygen basic is extension of o2 assembler.
i hope you get it now...

[Tomaaz]

Aurel, you don't have to explain me the difference between assembler and machine code, because I used to program in both (mostly in machine code). I would rather like to know your opinion about those memory leaks. There are several options:

1. You did something wrong and there is a problem with AurelBasic source code.
2. Author(s) of Emergence Basic did something wrong and there is problem with assembler code generated with it.
3. Author(s) of NASM did something wrong and there is problem with machine code generated with it.
4. You and author(s) of Emergence Basic did something wrong.
5. You and author(s) of NASM did something wrong.
6. Author(s) of Emergence Basic and author(s) of NASM did something wrong.
7. You, author(s) of Emergence Basic and author(s) of NASM did something wrong.
8. No one did anything wrong and those memory leaks are result of a miracle.

So, what is your opinion?

[Aurel]

Aurel, you don't have to explain me the difference between assembler and machine code, because I used to program in both (mostly in machine code). I would rather like to know your opinion about those memory leaks. There are several options:

1. You did something wrong and there is a problem with AurelBasic source code.
2. Author(s) of Emergence Basic did something wrong and there is problem with assembler code generated with it.
3. Author(s) of NASM did something wrong and there is problem with machine code generated with it.
4. You and author(s) of Emergence Basic did something wrong.
5. You and author(s) of NASM did something wrong.
6. Author(s) of Emergence Basic and author(s) of NASM did something wrong.
7. You, author(s) of Emergence Basic and author(s) of NASM did something wrong.
8. No one did anything wrong and those memory leaks are result of a miracle.

That you know the difference you probably will not say
"mostly in machine code"
which is 01010111000010101
Everybody can confirm this 

And i really don't get it what kind of answer you espect 

[Aurel]

To addition...if you interested i have found only this thing somewhere
on internet:

Submitted By: nasm64developer (nasm64developer)
Assigned to: Nobody/Anonymous (nobody)
Summary: memory leaks in %IF*, %ELIF*, and %UNDEF

Initial Comment:
The preprocessor has a memory leak in all %IF-type
directives, all %ELIF-type directives, as well as
in the %UNDEF directive. (The latter only kicks in
if there is trailing garbage, though.)

or maybe this:

However, NASM 0.98.xx still suffers
from a number of memory leaks, as well as a
number of bugs which can lead to core dumps.

Is this enough for you ?
Maybe is EB version of NASM one of them...
I really really don't know....

[Tomaaz]

That you know the difference you probably will not say
"mostly in machine code"
which is 01010111000010101

Yes, it is. But only from computer's point of view. This is all about numbers and they can be written in a different systems. In case of 8-bit computers it can be 254 12 3 or fe 0c 03. Of course for the computer it is 11111110 00001100 00000011. But they are exactly the same numbers. Some of them represent CPU commands, others - parameters to be used with these commands. You just need to place the numbers to the memory and tell computer from what address it should start read them. This is programming in machine code - when you put numbers directly in to memory and then tell the computer where they are. When you're writing in assembler (the language, which is almost the same as machine code), the assembler (the program) is doing it for you so you don't have to, for example, calculate manually values for jumps etc. This is how it looked on 8-bit machines. Now, probably, it looks a bit different, but general rules are, probably, the same. You've never done anything in assembler or machine code, have you? Sorry, but I really don't know if you have no basic knowledge about those things or it is just your English. And to be honest - I'm just a little bit drunk.

And i really don't get it what kind of answer you espect 

That was a joke. Who cares if the problem is with NASM or Emergence Basic. There are memory leaks and that's what important. Even if the problem is with NASM, Emergence Basic is a bad tool, because it uses faulty assembler.

[Aurel]

Even if the problem is with NASM, Emergence Basic is a bad tool, because it uses faulty assembler.

And you are little bit drunk...man what is wrong with you ...  
Maybe you have some sort of memory leak...hehehe.
I know that you fooling around with me, but why you so insist on this thematic?
Assembly programming i do long,long time ago on ZX Spectrum...
however forget...