Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
A Toy Soldier
@iamthecarisma_twitter

Between, why can block outside the class change values? That's odd.

It the normal standard of most high level languages, java, python e.t.c

By the way am working heavily on graphics module and fulltick by early next month we l have a small REPL and terminal for simple-lang on android to run and debug simple-lang on the fly
Abdulazeez Abdulazeez Adeshina
@Youngestdev
Hmmmm. Sounds nice.
Any update on the modular ?
A Toy Soldier
@iamthecarisma_twitter
Am waiting for you guys input on the ampersand & implementation
appcypher
@appcypher
I'm afraid you are adding a learning curve to the language if you make user to specify refs different from vals.
Everything (except primitive types maybe) should be passed by reference by default, because:
  • that's what is most dynamic languages (ruby, python, javascript, even java) and that's what users will expect
  • it is efficient both performance-wise and memory-consumption-wise
  • users can always use a .clone() or sth similar if they want a copy of the object
A Toy Soldier
@iamthecarisma_twitter
alright
A Toy Soldier
@iamthecarisma_twitter
Hello i am getting rid of the 'self' keyword and leaving only 'this' the two are pretty much the same except they clash sometimes so am removing 'self'
Abdulazeez Abdulazeez Adeshina
@Youngestdev
ideally the both of them are supposed to be working different I think we did not get the context in which they're supposed to work you know so I may be before moving actually I want you to digress into both of them you know so you can actually know what's going to happen
A Toy Soldier
@iamthecarisma_twitter
self is the actual or active object while this is used when the object scope changes, am keeping it, i ll write a blog to clarify the different
A Toy Soldier
@iamthecarisma_twitter
We need to follow same patter of code anyone building core module for the simple-lang should use the bracket instead of end for statements and no need to terminate the block with and end
New Module Standard
class Module : Object

    block Module()
         if true {

         }
A Toy Soldier
@iamthecarisma_twitter
It of great advantage to inherit object as it now has some very useful blocks from classes. Such as toString, modulename
no need to explicily declare OBJECT_NAME and OBJECT the object name and absolute name is stored in the Object class
e.g when a class inherit Object this blocks are loaded
@ourClass.classname() #will return the name from reflection e.g List
@ourClass.modulename() #will return the module name from reflection e.g simple.core
@ourClass.absolutename() #will return the absolute name from reflection e.g simple.core.List
and also for whatever you are printing to console kindly don't use @ and display use this instead
call simple.utilities.Console

stdout.println(yourobject) #to print an object to standard output
stderr.println(yourobject) #to print an object to standard error stream
A Toy Soldier
@iamthecarisma_twitter

using the blocks from Console will even allow any kind of object to be printed in a very pretty manner. If the object does not inherit 'Object' and does not have it toString() block you can send true as extra parameter to create a printable string from the object e.g

test = new Test
stdout.println(test) #prints => (this object cannot be printed)
stdout.println(test,true) #prints => [module.Test:x=10,y=10] 
class Test
   x = 10
   y = 10

stdout.println(test,true) actually created a printable string from the object

I ll develop the Console module more and blog about it
Sonkeng Maldini
@sdmg15
Hello guys ! A new contributor setting up :smile:
Still to figure out various stuffs before really diving
Abdulazeez Abdulazeez Adeshina
@Youngestdev
Welcome @sdmg15
A Toy Soldier
@iamthecarisma_twitter
Welcome @sdmg15 You can ask questions to get started with building on your system
Busari Habib
@Bahat159
Hi all
A Toy Soldier
@iamthecarisma_twitter
Welcome @Bahat159 Great to have you on the team. Looking forwarrrrrd to your contributions
Sonkeng Maldini
@sdmg15
Hello y'all
Is there a roadmap for simple? I mean different feature planning to implement etc
A Toy Soldier
@iamthecarisma_twitter
A Toy Soldier
@iamthecarisma_twitter
Hello guyz there is a new programming language called Yorlang which keyword are in yoruba. Sounds like fun but i see it as an esoteric language as foreigner might find it hard to code.
Meanwhile simple-lang keywords can be change to any language on earth which mean our display can become sope in yoruba or 显示 in china . The feature will be included in our next release
after this next release we can go all out on documentation, wiki, rosetta code and publications
A Toy Soldier
@iamthecarisma_twitter

Hello y'all

Have you been able to build it ?

Busari Habib
@Bahat159
@iamthecarisma_twitter No bro, don't include what's not. Implementing such shows you don't have a roadmap of what you want to achieve.
A Toy Soldier
@iamthecarisma_twitter
We be got roadmap here
A Toy Soldier
@iamthecarisma_twitter
Adding the dynamic keyword feature as as an hidden and advance advantage, imagine if you could read and write a code in your language. A pure code which will can be written in infinite different language and still run on the same vm, simple-lang is a feature pack language where you get to use whichever feature and can ignore others while still keeping it simplicity
People tends to accept something that embraces their culture and language it not racist it nature
I can't really decide for the language on my own. So here is a pool. If you accept dynamic keywords you should type yes and if you do not type no. An example of a dy keyword feature is
A Toy Soldier
@iamthecarisma_twitter
display "hello world" and in youruba ck(display, sope) sope "hello world"
Abdulazeez Abdulazeez Adeshina
@Youngestdev
I disagree with the implementation of otheer languages. It looks like rivalry and a lil bit childish
Busari Habib
@Bahat159
Thanks for the opinion Abdulazeez
A Toy Soldier
@iamthecarisma_twitter

I disagree with the implementation of otheer languages. It looks like rivalry and a lil bit childish

Only for the fact that it part of the simple-lang primary implementation. I call it flexible syntax.
You can check the earlier git commit from early febuary it has the feature but commented out trying to make it a main release feature
https://github.com/simple-lang/simple/blob/b7e86692d25166f6fb373a5eaafa1236db381a87/bootsrc/sources/simple_scanner.c line 584

Since it has two thumb down from within it ll remain commented till this Panel want it out or it remain commented forever
Busari Habib
@Bahat159
That's the problem you have bro
You won't fucking listen
A Toy Soldier
@iamthecarisma_twitter
The f and n words are not allowed
It has never been implemented and I did not say I will
Tochukwu Nkemdilim
@TNkemdilim
I'll say that we stick to constructive criticism. @Bahat159 ...
Even before @iamthecarisma_twitter said it in his message, the feature had long existed. I also remember seeing the commented code like around August or September.
Tochukwu Nkemdilim
@TNkemdilim
Also, I see no harm is such existed. Although, I'm not saying it should exist either. I'M, it's not currently pivotal decisions for Simple's current roadmap. Also, even if such feature were to be enabled, it would have to be based on a decision drawn out from a wide range of language adopters e.g. maybe a survey.
Even if such a feature were enabled, variations of the lang would never be our sole responsibility to develop. Such a feature could be used by acedemia's, compiler enthusiasts or maybe people who love to hack around stuffs.
Tochukwu Nkemdilim
@TNkemdilim
For example, as a compiler enthusist, from the commented implementation, i learnt a new approach to achieving this. Even if I never implement such feature in any compiler or interpreter Iater on, at leat it's worth learning.
For me, it all boils down to if the lang adopters want it or not. But I'll say it remains commented pending that time. And now isn't the best time for a go-ahead, because Simple us still in infancy
This are just my sole opinion and I'll be happy to be critized and corrected
Tochukwu Nkemdilim
@TNkemdilim

Also we shouldn't say the feature in Simple is rivalry. This is something that any language core team could merge if:

  1. It is inline with the compiler's goal and objectives
  2. Adopters we it as a valuable feature
  3. It profers a competitive advantage over seemingly competing language
  4. Isn't costly to implement
  5. We aren't trading performance for the feauture
  6. Etc.

Also if we were to compare it with yorlang. I don't suspect yorlang will be developed into becoming a fully mature laguage, based on examining the language owners point of view.

For me, what I'll also want to know is Simple's vision. As the only closely related statement I saw about this on the readme is,

"SIMPLE is a plain and innovative programming with multi-paradigm. It can be embedded in C/C++ projects. The language is portable to various OS including windows, macOS, any linux and unix distros and other OS. The language is small and fast."

For emphasis: a plain and innovative language .

Of which such a feature falls under.

Hence it's better to come up with a more concise vision statement, if that was not what was meant.