Restored from previous forum. Originally posted by Danilo.
Hello ricardo !!
I can understand you too.
But i think its not needed:
>Well, let me make my own unoptimized LIbs ha ha
>I want to learn, thats all.
Yeah, and everybody is writing LIBs then.
Professionals and Newbies too.
You loose 5 clocks here, 23 clocks there,
and 400 clocks in this Procedure.
I think thats not the thing PB is made for -
slow and bloated code.
If every Beginner can make own LIBs,
its the "start of the end" of the optimized
PureBasic.
>Maybe if i can make my LIBs directly from PB
>and see my commented ASM source, then i can learn a lot,
>because every change i made i will check again, etc.
Its the *same* if you put a procedure in
your Source and look at the generated
ASM-Output (if you can read it).
Look at the ASM-output and see what happens
if you use "a = a - 1" instead of "a-1"...
>Yes, but if we think in that way, then why
>does PB uses LIBs instead include files?
The PureBasic LIBs are only Assembly .OBJ-Files
and Description files for the Commands inside the LIB.
If you know ASM, you would understand how the
.OBJ-stuff works.
>Because its easier (and maybe some other reasons)
No, its not easier - its nearly the same.
Yes, there are 2 differences:
1.) you have to use the include command
for your Procedure-file (wow, big problem
2.) The Description file is missing, so you
dont get help for the new command/procedure (F1).
Point 2 is a seriously problem.
Forget point 1.
>I want to learn thats why i ask this feature.
>I imagine that every new user want to learn and
>maybe a lot of them will think in the same way
>that im thinking now.
Do you want PureBasic to become bloated
and slow like Visual Basic ??
If you dont want that, you should (try to)
understand why its not good that every
Beginner can code own LIBs.
I can understand your thinking
and you cant understand me.
If you were a Assembly programmer for a few
years you would understand my point here...
cya,
...Danilo
(registered PureBasic user)