There are a few I’m aware of:

  1. Rust-style use (multiple imports per statement, renaming items using as)
  2. Java-style import (single import per statement, no renaming (afaik))
  3. Zig-style let xlib = @import("xlib") (imports as assignments)
  4. C-style #include (no importing, just pastes the code of the named file)
  • terabyterex@lemmy.world
    3·
    3 days ago

    you can also tell them java cant handle.pointers. i have worked with a lot of backend c code using c#.

    not sure about the following but:

    can you control how a struct is handled in memory in java? (had tto do this with a c# front end calling a credit card verifyling service/library written in c++)

    do they have value types?

    • Traister101@lemmy.today
      1·
      3 days ago

      Java doesnt have value types or structs. You have primatives (booleans, integer types and float/double) and then everything else (even the uppercase primative types like Boolean) are reference types, IE on the heap. For stuff that plays with pointers you generally just call into native code, get back a long (the pointer to whatever you just allocated) and you call into native code to do stuff with the pointer. Native code can make a proper java object but it’s involved and has all the same cons as allocating one in Java land.

      Supposedly records (a pseudo struct) might get stronger optimization options (IE put on the stack) but fundementaly reference types are just pointers and if you get an object via constructor or parameter the language must support you putting it in global state

    • programmerlexi@sh.itjust.worksOP
      2·
      3 days ago

      You cqn’t really control the layout as that would prevent the JVM from reshaping your classes (which is a fundamental requirement for things like Dalvik (android jvm))

    • nebeker@programming.devEnglish
      1·
      3 days ago

      Conversely, I’ve written C++ code to into DLLs interop with .NET. It makes a lot of sense given what .NET was developed for.