undefined | Better HN

0 pointshacksoi6y ago0 comments

#include causes the preprocessor to replace it with the specified file. Why is that bad?

0 comments

Because ostensibly we've moved on from that to the concept of actual modules.

'including' stuff entails a whole host of ugly things including multiple definitions, circular dependencies etc. etc..

Most languages use some kind of module resolution, which when specified clearly is usually better. Of course sometimes they forget to define things, and leave us in a lurch ... but hey ...

Aardappel6y ago

You're reading too much into the keyword.. in Lobster, this does never include anything twice. Circular dependencies just work, without having to pre-declare anything. I should probably rename it.

sonnyblarney6y ago

I suggest people might pick up on that pretty quick, maybe no need to rename given some random comment. That said, maybe you want to have a gander through the various languages and see what words are used for what, and if there's a 'standard' go with that :)

Cool language though. I love everything except for the name, sorry :)

1 more reply

j / k navigate · click thread line to collapse

0 comments

sonnyblarney6y ago

Because ostensibly we've moved on from that to the concept of actual modules.

'including' stuff entails a whole host of ugly things including multiple definitions, circular dependencies etc. etc..

Most languages use some kind of module resolution, which when specified clearly is usually better. Of course sometimes they forget to define things, and leave us in a lurch ... but hey ...

Aardappel6y ago

You're reading too much into the keyword.. in Lobster, this does never include anything twice. Circular dependencies just work, without having to pre-declare anything. I should probably rename it.

sonnyblarney6y ago

Cool language though. I love everything except for the name, sorry :)

1 more reply

j / k navigate · click thread line to collapse