Welcome to the world of abusing the shit out of Ant. My first full time job was developing Ant in unholy ways. Tens of thousands of lines of Ant at least, doing significant logic. If-then-else, for loops, math, procedures, date-time math. I stuck it out for a year. It was a year too long.
I like it, this is clearly very enterprisey and solution focused, but I would like to suggest a couple of amendments if I may?
Namespaces
We should make full use of namespaces. Make the structural tags be in a language specific namespace (to be referenced in every function spec, obviously) but change the in an out params to use the parameter name as the tag, namespaced to the function they’re for, with a type attribute.
In memory message queues
Have all function invocations be marshaled as xml documents posted to an in memory message queue. Said documents should use a schema that validates the structure and a function specific schema to validate the types of arguments being passed. Namespace everything.
I reckon we could power a medium sided country if we could generate energy from the programmers despair.
statement: comparison:-kind: libcompare.EQUALScomparators:-foo-barwhentrue:statement: streaming: -kind: libstreams.PRINTcontent:foo equals barwhenfalse:statement: streaming: -kind: libstreams.PRINTcontent:foo does not equal bar
It uses XML-like syntax:
<fun> <name>sum</name> <in> <int>foo</int> <int>bar=0</int> </in> <out><int>foo+bar</int></out> </fun>This deserves to be added to the list of human rights violations
<fun> <name>sum</name> <in> <int> <name>foo</name> </int> <int> <name>bar</name> <default_value> <int>0</int> </default_value> </int> </in> <out> <int> <calculation> <numerical_operation> <operator_plus> <operand> <var>foo</var> </operand> <operand> <var>bar</var> </operand> </operator_plus> </numerical_operation> </calculation> </int> </out> </fun>How did you come up with such a ****ingly stupid syntax?!
It haunts me in my dreams
Thanks, I hate it.
Welcome to the world of abusing the shit out of Ant. My first full time job was developing Ant in unholy ways. Tens of thousands of lines of Ant at least, doing significant logic. If-then-else, for loops, math, procedures, date-time math. I stuck it out for a year. It was a year too long.
Thankfully we have Gradle now.
The whitespace is not only required, but it must be tabs and spaces.
Calm down, Satan
Compiler rolls the dice if your only required indentation is accepted as space or tab. Per line.
But stores this information as a metadata file, which gets invalidated when a new file is added/removed from the program muhahaha!
I like it, this is clearly very enterprisey and solution focused, but I would like to suggest a couple of amendments if I may?
Namespaces We should make full use of namespaces. Make the structural tags be in a language specific namespace (to be referenced in every function spec, obviously) but change the in an out params to use the parameter name as the tag, namespaced to the function they’re for, with a
typeattribute.In memory message queues Have all function invocations be marshaled as xml documents posted to an in memory message queue. Said documents should use a schema that validates the structure and a function specific schema to validate the types of arguments being passed. Namespace everything.
I reckon we could power a medium sided country if we could generate energy from the programmers despair.
Can you please link to a medium article on how this will help utilize AI blockchain so i can show it to management on Monday?
Make sure to make ample use of mixed content elements.
<statement><var>bar</var> = <int>0</int></statement>statement: comparison: - kind: libcompare.EQUALS comparators: - foo - bar whentrue: statement: streaming: - kind: libstreams.PRINT content: foo equals bar whenfalse: statement: streaming: - kind: libstreams.PRINT content: foo does not equal barGod I hate it
Lol, I’m sorry
Don’t apologize, it’s beautiful in its horribleness
You monster
Who hurt you :(
Oh my, I feel woozy …
The tag indentation is a required part of the syntax and don’t forget colons at the end of the tag
That’s basically how the Android app Tasker works. You do the programming through its UI, but when you export/share your tasks, they’re saved as xml
I took every coding class my highschool offered, and the only thing that drove me more crazy than this syntax was trying to use CSS.
That’s because you didn’t try our lord and savior SASS. Vanilla CSS should be illegal at this stage.
I almost did similar with SDLang as I was very desperate for a scripting language, but now I have a wasmtime API for D.