DEV Community

Jonyk56
Jonyk56

Posted on

1

Xent.fx devblog 2

well, I overshot my goals... .

Hey folks! Been a lil' bit but I have news!
Xent has entered the gamma stage of development and we are seeing a release for 0.2 alpha sometime in november...

for now, enjoy some fancy import export code

$DEF
@use[xcore]
&using[xcore] mks [io/in;;io/out] 
$MSP
cspace _[]{
   set _PlaceA as "work trying to make xent.fx a great language!" {ANY} %%type defs and variables :D
   %% type defs are: space (namespace), table (array/dictionary), cls (not usable yet), int, bool, double, ANY, str, chr, b8,ub8,b16,ub16,b32,ub32,b64,ub64
   in#put("heya folks! I am at ${get _PlaceA &&}") %% the &&} has a use I will explain in the future but for now just know it makes get work inside of the text!

}
Enter fullscreen mode Exit fullscreen mode

Now let's explain this code...

line 1. $DEF
the $DEF tells xent that you are about to import a whole lotta things

line 2. @use[xcore]
xcore is the library of gods, if you wish to use anything that xent provides without an external source, xcore is the way to obtain that resource

line 3. &using[xcore] mks [io/in;;io/out]
io/in and io/out are swapped! compared to most languages, in is the way you get inputs from console, but in xent this is swapped and for good reason I will explain in alpha tests. The same situation is for out, out is the input from console.

line 4. $MSP
(c) microsoft project this literally is where the code truly starts, anything below this can be used and called ANYWHERE, while anything inside of a space can only be called when 'included'

line 5. cspace _[]{

cspace

the main code, this name may be changed but know it stands for the "direct call space"

_

"RUN ME FIRST"

[]

if you want to get a system variable, place it in these brackets (non exist yet)

{

if you know javascript you know what this is.

line 6 needs no explanation.
line 7 needs no explanation.

anyways now that you've seen the newest xent example, lets talk about a few specifics
xent will be a micro c++.
how xent will work is it will be compiled into c++ code and the compiled further into a proper executable.
The reason for this is to make xent actually have a purpose as an intended to be easier language that works just like c++ and will allow you to see the c++ code that came out of the xent code.

Seems like a buncha crap don't it?
Yea it does but you gotta put some faith, Xent is like CoffeeScript. Xent will be like Typescript. Xent is coming.

Sentry image

See why 4M developers consider Sentry, “not bad.”

Fixing code doesn’t have to be the worst part of your day. Learn how Sentry can help.

Learn more

Top comments (0)

Postmark Image

Speedy emails, satisfied customers

Are delayed transactional emails costing you user satisfaction? Postmark delivers your emails almost instantly, keeping your customers happy and connected.

Sign up

👋 Kindness is contagious

Engage with a sea of insights in this enlightening article, highly esteemed within the encouraging DEV Community. Programmers of every skill level are invited to participate and enrich our shared knowledge.

A simple "thank you" can uplift someone's spirits. Express your appreciation in the comments section!

On DEV, sharing knowledge smooths our journey and strengthens our community bonds. Found this useful? A brief thank you to the author can mean a lot.

Okay