ODZNAMES: What happens to the local server?

Malicious intrusion attempts have been initiated. In the near future, all malicious software running on the yada will try to block new applications written in that language in the struggle with those who try to gain access to uninfected folders.

I ran the first bad site cleaning tool I wrote with that language on my server. The results seem impressive to the general public. When administrators access unauthorized access to the system, server logs are automatically checked for errors, and sites and accounts are automatically deactivated in a server-side query.

In addition, all servers added to the blacklist are disconnected before they can connect to the server. This increases server security. I’ll share the source code for it after the tests are over in the coming days. In the meantime, many sites were blacklisted and their accounts were closed.

O Language: Web Site Update

The website of that language has been renewed. We converted the site to a documentation site in order to use it more efficiently. So we will create the documentation directly by hovering over the site. You can search by direct documentation.

For example, if you use the term “file” directly on the site, you can make automatic assignments like “Files”. We made searches and corrections in the post. We have adapted our documentation to the most recent version.


These types of optimizations will be effective both in terms of google and site. While doing such optimizations, we have updated the site design. You can visit olang.space to see the updates.


O Language: Exception Management

Exception management is an array that allows you to check whether an error has occurred depending on an object. The content is checked to see if there is an error, or to the end if no error has occurred.

Begin is used to control an object.

begin object{

“Expect” and “recover” are used to debug and print out errors. Automatic “error” identification is done. In this way, we can use this definition as an internal variable.

begin object{
   if (test == "hello"){
     except test "Hello is not usefull. Please use Hi on project."

   recover test{

If no errors are received, “final” is used. If there is no error in this way, the values in “final” are automatically executed.

def test = "hello"
begin object{
   if (test == "hello"){
     except test "Hello is not usefull. Please use Hi on project."

   recover object{

   final object{
      println("Hello is not used. Yay!")

This is how we debug it. Exception detection can be used in this way.

Web site: http://olang.space/

Source: http://olang.space/begin

O Language: Build 4.1

A new version has been released for that language. A number of critical updates and fixes have been made in this release. Fixed unknown IDENTIFIER and similar critical problems in function definitions. In addition, the replace function has been added.

This function can be used to change strings and change strings;

def test = "test"
def test = replace(test, "test", "olang")
#=> olang

You can reach the details of the latest version via this link.

Web site: O Language

O Language: First Router

The router socket structure was created with the intention of creating an API over the HTTP/S protocol and exchanging data through the socket. In web based projects it is possible to write web server quickly and easily. In addition, the API can be created in micro-services.

hello.olm (as hello module):

def hello = fn(name){
 return "Hello, "+name+"! Welcome to Olang"

router.ola (as router script):

load "hello.olm"

def config = {
 "GET" : {
 "/" : "Welcome to the O-Lang Router!"
 "/:name" : hello("{{.name}}")

show("Listening Ctrl+C to exit.")
router("8080", config);

GET method test:

~> curl -X GET localhost:8080
Welcome to the O-Lang Router!

POST method test (oytun as parameter value for name [ :name => {{.name}} ]):

~> curl -X POST localhost:8080/oytun
Hello, oytun! Welcome to Olang

As you can see in the example, we wrote a web micro service using port 8080 via get and post methods.