embed.fnc: Remove obsolete comments:

khwilliamson · khwilliamson · commit c20589c549d5 · 2024-10-23T08:55:42.000-06:00
Linux and Darwin now can have hidden visibility
diff --git a/embed.fnc b/embed.fnc
@@ -52,10 +52,9 @@
 :
 : The default without flags is to declare a function for internal perl-core use
 : only.  The short name is visible only when the PERL_CORE symbol is defined.
-: On some platforms, such as Linux and Darwin, all non-static functions
-: are currently externally visible.  Because of this, and also for programs
-: that embed perl, most non-static functions should have the 'p' flag to avoid
-: namespace clashes.
+: On some platforms all non-static functions are currently externally visible.
+: Because of this, and also for programs that embed perl, most non-static
+: functions should have the 'p' flag to avoid namespace clashes.
 :
 : There are several advantages to using a macro instead of the full Perl_foo or
 : S_foo form: it hides the need to know if the called function requires a

Original file line number	Diff line number	Diff line change
`@@ -52,10 +52,9 @@`
`52`	`52`	`:`
`53`	`53`	`: The default without flags is to declare a function for internal perl-core use`
`54`	`54`	`: only. The short name is visible only when the PERL_CORE symbol is defined.`
`55`		`-: On some platforms, such as Linux and Darwin, all non-static functions`
`56`		`-: are currently externally visible. Because of this, and also for programs`
`57`		`-: that embed perl, most non-static functions should have the 'p' flag to avoid`
`58`		`-: namespace clashes.`
	`55`	`+: On some platforms all non-static functions are currently externally visible.`
	`56`	`+: Because of this, and also for programs that embed perl, most non-static`
	`57`	`+: functions should have the 'p' flag to avoid namespace clashes.`
`59`	`58`	`:`
`60`	`59`	`: There are several advantages to using a macro instead of the full Perl_foo or`
`61`	`60`	`: S_foo form: it hides the need to know if the called function requires a`