Nim: Scripting Ease in a Compiled Language

Re:Nim: Scripting Ease in a Compiled Language by treeform on Wednesday October 30, 2019 @07:53AM (#21396652)

Main reason for this feature is that Nim is big as a glue language. Many C/C++ libraries don't have consistent naming conventions between them. I don't want my code to look like a patch work of `__APICALL__(system_call.inspectSomething())` I just want it to look like Nim code: `apiCall(systemCall.inspectSomething())`. This is just a consistent standard on how to turn names in one style into another style backed into a language.

[ Parent | on HN ]

Re:Nim: Scripting Ease in a Compiled Language by airstrike on Wednesday October 30, 2019 @11:52AM (#21399053)

    apiCall = __APICALL__

done

[ Parent | on HN ]

Re:Nim: Scripting Ease in a Compiled Language by beagle3 on Wednesday October 30, 2019 @07:05PM (#21403947)

So you are writing hundreds of rename rules.

Well, unlike treeform, I like it to be:

    api_call(system_call.inspect_something())

Which I find much more readable. What now?

[ Parent | on HN ]

Re:Nim: Scripting Ease in a Compiled Language by treeform on Wednesday October 30, 2019 @05:06PM (#21402728)

Then you are writing or auto generating these giant 1000s of lines long files with renames... why?

[ Parent | on HN ]

Re:Nim: Scripting Ease in a Compiled Language by airstrike on Tuesday November 05, 2019 @10:56AM (#21453472)

I never said it was a good idea!

[ Parent | on HN ]