Learning DeadCL DeadCL Tutorials DeadCL Syntax DeadCL MBS

Walk throughs

Author Keys Conversations Libraries Arrays

  Network Status Community Hub Contact Us



Preprocessor

(deadCL Syntax)


deadCL uses preprocessors to ensure essential objects are available before the files (Conversation) is run.

They're among the easiest components of deadCL to understand, the following examples should aid in your understanding - if you have any questions best to visit our Community hub.





*

Required to load (will always try trusted files first then local) before executing next action.

Examples



Within deadCL we use * to inform when an object is required. While you can insist any object or remote resource is required it's sensible to use it sparingly.



For example we use * before any required input resource;

*input, @INPUT-ADDRESS


As without Libraries deadCL won't function every initial Library load requires it;

*Catch-lib -R @LIBRARY-DEAD-ID *Catch-all - libs


Every Conversation needs to "close the loop" because of this the function also requires a *

It's also worth noting all Conversations must end using this command string.

*end* *end



dld.keyset

Prompt for Author key evaluation

Examples



Within deadCL we use dld.keyset for one thing alone, to request and evaluate if the Author key has permitted the Conversation or Library to be ran against it.



For example we use dld.keyset within a (some) Conversations when the author wants an added layer of protection;

This prompts deadCL to check the do-ID matches the trusted Author Key.

dld.keyset('YOUR-AUTHOR-DO-ID')



- -

Connect two statements

Examples



Within deadCL we use - - to link to objects/statements together. You'll see it across all mediums including Author Keys.



For example we use - - to connect MBS (meanings Based Syntax) to deadCL syntax commands this unique combination allows for an extensive range of requests.

For example here are three different ways of achieving the same outcome, one in using deadCL the next a mixture of both deadCL & MBS while the last is just MBS.

?bnd -- @_all *REQUEST bnd -- @_all *FORCE SET -- ALL VALUES



_imprt

Used to import information

Examples



Within deadCL we use _imprt to import objects/remote resources, while this action is performed (predominantly) using MBS in our offical Libraries it's advantageous to understand how to use the command.



For example we use _imprt to denote where certain resources can be located for KC's (Key Commands)

This enables dynamic value and fixed values - in effect the same as MBS "@import"

DUFFER; _imprt {@domain.com/duffer.dead}


For example we use _imprt to insert fix object information into a command.

This code snippet lists the contexts of the remote library "DAW_2019" within the Conversation.

_imprt -- @ID_ DAW_2019, LIST



CALL -

Call-after function, useful for interpretation

Examples



Within deadCL we use CALL - to call upon a resource previously loaded in the Conversation, remember deadCL runs each library from the start till it finds the object information requested - this function speeds up requests by enabling you to call a resource again without requesting the entire library.



For example we use CALL - to make object interpretations multiple times.

This example checks three different objects are "spades" yet different colours.

CONFIRM -- SPADE CALL - @spade-black.dead CALL - @spade-red.dead CALL - @spade-green.dead


You can also use CALL - to avoid having a object interpretation changed

For instances here we're calling upon an object 'thoughts' to post it directly

CALL - {"thoughts"} -- POST



$POST

Used to set the DeadLetter post address in a URL, should always be followed by '@'

Examples



Within deadCL we use $POST to create unique deadIDs this is commonly used within our Author Keys. has the command forces the creation of resources at post.deadletter.io



For example we use $POST to create the post address 'https://post.deadletter.io/do-id+conversation-url'