You must log in or register to comment.
all lines not terminated by a single space are comments
There’s a special place in hell for you
Also each line starts with a semicolon and you have to escape spaces in strings using a double forward slash
I realized a while ago that there’s nothing stopping me from writing rust like this
;println!("This is great") ;println!("I think everyone should write rust like this") ;println!("Probably works in most languages that use semicolons") ;Nasm programmers probably think that is old code that you commented out.
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><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>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.
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 bar
…and it’s compiled
…to an intermediate set of instructions for a virtual machine…
…called the brainfuck interpreter
Make CScript, an interpreted, duck-typed language
Relevant commitstrip: https://www.commitstrip.com/en/2019/02/25/pythonscript/
Make a UX or Project management tool with “Java” in the name so newbie recruiters look for people in the wrong department.
They already do this, but this would make them do it even more.
Make it purely functional, lisp based with reversed Polish notation and APL symboles, I dare you mf
Make it completely ignore indentation
Make it completely untyped. Everything’s just a string.
I think white space should be used to represent basic functions too. For example 3 spaces can be used to sum two values while 4 spaces can be used to subtract.
Confusion like this got me my current job. They were looking for somebody with experience in “Microsoft Endpoint Configuration Manager”, and I look that up and I’m like “Oh, that’s SCCM, I do that”. Go through the interview process they keep asking me if I know Endpoint Configuration Manager and I’m like “yeah, for sure”. I get the job. Day one, the other systems engineer is like “here is the link to our Endpoint Manager Tenant”, and I’m like “oh… Shit I have never ever used this”
Well… Ends up Endpoint Configuration Manager and Endpoint Manager are two different things. Fortunately for me they are pretty similar in function and rely on knowledge of Windows and Powershell, which I know.
So my first 2 weeks of work was taking a shitload of courses in Endpoint Manager and watching a lot of videos and learning it inside and out.
2 years later and I’m an Endpoint Manager/Intune pro.
90% of IT and software jobs are “I have common sense, know how to look up information, and my boss is intimidated by my work so they don’t question it.”
So the matlab thing where all lines not terminated by semi colon are printed except use Greek question marks instead of semi colons.
I like this but to make the code more readable the Greek question mark should also be placed upsidedown at the start of every line that needs to not be printed.
Should it raise an error of treat it as a comment for lines with neither? Im leaning towards treat it as a comment will make debugging harder.
I agree. If there is no Greek question mark at all it should be code that is printed to console. If there is an upside down at the start and upside right at the end it is just normal code. If upside right at the end only, it is a comment. Only upside down at the start it will be treated as debug specific code and will not be run in production compilations.
