Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc: replace harr HTML entity by unicode #53066

Merged
merged 3 commits into from
Jan 29, 2024
Merged

doc: replace harr HTML entity by unicode #53066

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8f84e49
doc: replace harr HTML entity by unicode
fingolfin Jan 26, 2024
f8cde5c
Merge branch 'master' into mh/harr
DilumAluthge Jan 26, 2024
6945fe5
Merge branch 'master' into mh/harr
DilumAluthge Jan 26, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions doc/src/manual/noteworthy-differences.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -353,7 +353,7 @@ For users coming to Julia from R, these are some noteworthy differences:
it's more general than that since methods are dispatched on every argument type, not only `this`,
using the most-specific-declaration rule).

### Julia ↔ C/C++: Namespaces
### Julia ⇔ C/C++: Namespaces
* C/C++ `namespace`s correspond roughly to Julia `module`s.
* There are no private globals or fields in Julia. Everything is publicly accessible
through fully qualified paths (or relative paths, if desired).
Expand All @@ -365,7 +365,7 @@ For users coming to Julia from R, these are some noteworthy differences:
* Caveat: `import`/`using` (Julia) works only at the global scope level (`module`s)
* In C++, `using namespace X` works within arbitrary scopes (ex: function scope).

### Julia ↔ C/C++: Module loading
### Julia ⇔ C/C++: Module loading
* When you think of a C/C++ "**library**", you are likely looking for a Julia "**package**".
* Caveat: C/C++ libraries often house multiple "software modules" whereas Julia
"packages" typically house one.
Expand Down Expand Up @@ -396,7 +396,7 @@ For users coming to Julia from R, these are some noteworthy differences:
* Directory-based package repositories are the **quickest solution** to developing local
libraries of "software modules".

### Julia ↔ C/C++: Assembling modules
### Julia ⇔ C/C++: Assembling modules
* In C/C++, `.c`/`.cpp` files are compiled & added to a library with build/`make` scripts.
* In Julia, `import [PkgName]`/`using [PkgName]` statements load `[PkgName].jl` located
in a package's `[PkgName]/src/` subdirectory.
Expand All @@ -413,7 +413,7 @@ For users coming to Julia from R, these are some noteworthy differences:
Julia package* ("software module"). It is therefore relatively straightforward to ensure
file are `include`d only once (No `#ifdef` confusion).

### Julia ↔ C/C++: Module interface
### Julia ⇔ C/C++: Module interface
* C++ exposes interfaces using "public" `.h`/`.hpp` files whereas Julia `module`s mark
specific symbols that are intended for their users as `public`or `export`ed.
* Often, Julia `module`s simply add functionality by generating new "methods" to existing
Expand All @@ -427,7 +427,7 @@ For users coming to Julia from R, these are some noteworthy differences:
* Users might be expected to access these components by qualifying functions/structs/...
with the package/module name (ex: `MyModule.run_this_task(...)`).

### Julia ↔ C/C++: Quick reference
### Julia ⇔ C/C++: Quick reference

| Software Concept | Julia | C/C++ |
| :--- | :--- | :--- |
Expand Down