The Box, development tool, "Structural programming"

[jdc]

The Box, Development tool.

Development software build for programmers.

Its build in C, but if you want another repository for other languages post in the comments.

It is on google drive : https://drive.google.com/drive/folders/ ... sp=sharing

Git Hub : https://github.com/saintsoftware/the-box

Discod : https://discordapp.com/invite/Mwgxgzf

Flattr : https://flattr.com/@jdc01

Facebook : https://www.facebook.com/The-Box-101342814696181

Chat on FB : https://www.facebook.com/groups/222288609064790

Blogg : https://thebox0.blogspot.com/

Help in Development : if you wish to help width the development send email to joao_canteiro@hotmail.com

[jdc]

outdated post ...

[jdc]

outdated post...

[Lyberta]

Deleted.

[jdc]

Thanks a lot for the feedback constructive criticism is always welcome.

I disagree lightly, Linux is build on C so is a good language after all. Agree that C could be a bit updated in some aspects. PHP push languages a lot forwards bringing new functionality and ways of doing things in new ways. In terms of innovation i think is a great language.

Most of the stuff that is in that article, i think is more a person that is not very creative, or don't like to solve problems. Of course is going to have problems with a loose language like PHP. If you are expecting the programming language just to allow things to be done in one way or very strict, but that cut off all your creativity. Can become extremely boring to code like that.

Other stuff they updated that in a regular basis last update was last month on 30 November, i have my doubts that the arrays are inconsistent, Facebook is build on PHP ...

But people can choose what they like...

[Lyberta]

Deleted.

[jdc]

outdated post...

[Julius]

Let's not make this into a "my favourite programming language it better than yours" discussion, please.

[dulsi]

Programming language isn't a big deal. You can write interesting games in any language. However, I have no idea what you are making. It's some sort of development tool. I don't know if it is C or PHP or both.

[jdc]

Julius : don't mind answering to people if that what motivates them to work. Knowing all the details.

Dulsi : it is stated clear that is done in C in Dropbox only contains files in C. But often project contains several languages. For example a database is made in SQL which have nothing to do with PHP or C. Engines like unreal have the core done in C++ and have biding's for Lua, or other high level scripting language.

[jdc]

outdated post...

[jdc]

outdate post

[dulsi]

Dulsi : it is stated clear that is done in C in Dropbox only contains files in C. But often project contains several languages. For example a database is made in SQL which have nothing to do with PHP or C. Engines like unreal have the core done in C++ and have biding's for Lua, or other high level scripting language.

Ok. But I don't see what that has to do with The Box. When announcing a project it is probably best to stay on that subject. If you want to talk about the merits of PHP or C or having other language bindings in a game engine, it is probably best to do that in another thread. I have now looked at your google drive. I still don't really understand what is The Box. Is it meant to be a game, a game engine, or some other development tool? You don't have a license specified for your code. In general I wouldn't include .c files with #include. Your suggestion of using 2 arrays to build lists of things is fine but most games store that sort of thing in data files now. That way you can modify the program without recompiling. There are times when combining the data into the binary is advantageous or necessary (for example my viobyte game needs to do so because the target platform is so limited).

[Lyberta]

Deleted.

[jdc]

outdated

[jdc]

outated post...

[jdc]

outdate post...

[jdc]

outdated post...

[smcameron]

i will need to digg a bit more to know how to do this stuff in C

Well, you aren't wrong about that.

No offense, but this thread comes off as slightly crazy. I don't think any C programmers have any desire to program C as if it were PHP. People who still program in C nowadays do so for a few reasons.

* They're doing low level stuff, and they need to control the hardware (e.g. set up virtual memory page tables themselves in a kernel).
* They are on a tiny machine with kilobytes of RAM and C is all that will fit.
* They have been programming in C for a long time and they simply like it -- they like simple imperative programming, they like doing their own memory management.

Note that the last reason is not a technical reason, it is simply a subjective preference.

You appear to be attempting to program in C somehow as if it were PHP, and to explain to other people how to do it (despite not appearing to be very good at either.)

This, for example, is utter nonsense:

How to handle variables ?

For example why to re declare pointers all the way in the project when we can have generic pointers declared :

int *int_pointer;
char *char_pointer;
float *float_pointer;

When we need to use them inside our files, we know that the structure have generic declared pointers. This is used in? A form of structure, so the template have this stuff build in. In your file you access the int_pointer.

Pointers are just a address to a variable they are not, a variable this means that it loads less stuff.

int large_number = 00987987987989890;

*int_pointer = large_number;

if we use our *int_pointer to pass it to a function, we don't move the variable around this is where we are saving resources. In our structure, we are saving lines of code by not re declaring stuff and by having pre build in variables.

Another pre build variable :

screen_width = 640;
screen_height = 480;

variables that :

why should we re declare this stuff which time we start a project?

This stuff should be a standard variable.

I think you should try programming in C for about 5 or 10 years and make some projects with it before attempting to explain to other people how they should use C.

[jdc]

oudated post...

[jdc]

outdated post...

[jdc]

outdate post...

[smcameron]

I use C the way i want, and i don't control other people topics. Nor do i make ironic comments, how to manage project's that i have no intention to help out. Talk comes cheap!

I was reading the forums, and seen this attitude before, people are doing some stuff that they like when others see some kind of competition, or project, they try to black out other people projects.

Great that this community try to help out others, and the administrators are active in looking in to this kind of situations.

I only appreciate constructive criticism and this one is not one of them.

Uh, I don't see you as "some kind of competition". Look, I've been programming in C since 1987. Based on what you've written, you seem like a novice at C. Very much so. I'm trying to tell you that as a novice, you shouldn't be offering advice on how to write C code. That's all. But if you insist, proceed. Just do not be surprised when people find your advice wanting. I'm trying to save you from further embarrassment. Not that you couldn't ever offer advice on how to write C code, but you're clearly not yet ready for that. (It's possible that you have some amazing new paradigm for C programming I'm too dumb to understand, but I don't think so, based on what I've read so far... e.g.

Pointers are just a address to a variable they are not, a variable this means that it loads less stuff.

int large_number = 00987987987989890;

Because that constant begins with 0, that means it's octal, so it's not nearly as big as it seems, and because 9 is not an octal digit, this doesn't even compile:

{l Code}: {l Select All Code}

error: invalid digit "9" in octal constant


If you intend to instruct others, you need to test your examples.

*int_pointer = large_number;

if we use our *int_pointer to pass it to a function, we don't move the variable around this is where we are saving resources. In our structure, we are saving lines of code by not re declaring stuff and by having pre build in variables.

What? On most systems nowadays (64-bit) an int is 32-bits and a pointer is 64-bits, so passing the pointer instead of the int is wasting memory at the very least. Passing a pointer doesn't make it any better. Not only that, why use the artificial "*int_pointer" rather than just:

{l Code}: {l Select All Code}

    my_function(&large_number);


You need to know at least the basics of C before you can instruct others, or write a reasonable library in C that you expect others to actually use. I'm trying to help you, not bash you. Spend some time with C, writing some programs, gaining some experience (years) before trying to tell people how to write C code.

[Lyberta]

Deleted.

[jdc]

outdate post...