It takes ≈ 6 seconds to start because it has to compute and store 76800 * 7 SINES and 76800 * 2 square roots in a table in order to get a decent execution speed

Also at the numbers.

Yeah it takes quite long to start but it looks AWESOME.

Looks nice. It reminds me the other plasma demo by Hoffa I think. Those animations actually reminds me of battle backgrounds in Earthbound.

BTW Rainbow Dash >> Derpy

In short, I don't really like the word "library" to describe bunch of code you reuse from one project to another.
This is most likely called "toolkit". A library is attended to be distribued and used by others and as far as I can see you're not willing to release it as a standalone library.

Maybe the word "library" doesn't apply yet but it will apply when everything gets released, which willhappen according to this quote (and also according to the several releases we see in the quoted topic).

So I wrote this library which I named nRayC, because it's an Nspire lib about RAYcasting to be used in C

Although this library is mainly focused on raycasting, it's not its only use : I also included a bunch of functions, like pixel, line and even triangle (why not) drawing, tile detection, bitmaps loading and stuffs.

Currently, the library features raycasting rendered by a unique function :

void nRC_rayCasting(int *map, Vector player, ScreenPoint mapDimensions, Vector dir, Vector planeVec, uint16_t *textures, char *buffer)

It also provides two structures as you can see, ScreenPoint and Vector. I don't release anything for now because I don't think it's ready to be released, but I attach a screenshot of what it can do

What Hayleia said. How can you judge me

Judging you ? Where is it question of judging people here ?

when you know nothing about what I wrote ?

I know about C programming on the TI-Nspire and the about the plasma demo, about your past projects and abut what you said in your post.
According to that I was able to determine the following without being able to look at the code :

It's exactly the contrary. I only use nRayC's setPixel function.

It is exactly what I'm trying to tell you, if you only use such a function, things are telling me you copy/pasted it in your code thus your not using a library but a tookit. There is a big difference between the two (copy/pasting vs compile time linking).

If you feel offended by my remarks where I'm trying to teach you good programming practice then I'm sorry and I promise not to help you in the future.
If, on the contrary, your using the proper to use a non-released-yet standalone library without copy/pasting your code from one project to another (since you're saying in a lot of projects that you're not using nSDL "because blablabla"), fine, but then please be more clear in the future, for example on how you managed to code a crossplatform setPixel that is not the Ndless nor the nSDL one ... (this caught my attention and was affraid you where boycotting nSDL for no reason).

Well yeah, it's badly said, I meant judging what I'm doing. I don't like how you say :

Quote from: Levak on June 22, 2013, 09:00:49 pm

In short, I don't really like the word "library" to describe bunch of code you reuse from one project to another.
This is most likely called "toolkit". A library is attended to be distribued and used by others and as far as I can see you're not willing to release it as a standalone library.

Without knowing that I only use a sole function of a whole engine that is already released.

This confirm what I was saying : you're calling "lib" the use (=copy/paste here) of a "sole function" from one project (nRayC) to another.
Since you did not corrected the other points of my previous post, I take them as true statement.

And the reason why I'm not using nSDL (and not "boycotting", it's a great lib) is that I really like to know exactly what I'm doing, not only to make things work like I want them to, but also to understand concepts.

For sure it is nice to understand on what your walking, but I'm not sure it is usefull to do it on every project you do, most likely wasting time.