Hacker Newsnew | past | comments | ask | show | jobs | submit | zwetan's commentslogin

see https://github.com/FastCGI-Archives

where you will be able to find FastCGI Developer's Kit sources and documentations


see here: https://pubs.opengroup.org/onlinepubs/9699919799/functions/e...

plenty of basic examples with execv, execve, execvp, etc.

if the execv() call succeed then it completely replaces the program running in the process that calls it

you can do plenty of tricks with that ;)


what if you need to distribute a .deb containing binaries that target other operating system ?

example: I got a tool that allow from any Windows/macOS/Linux to package a runtime+script to any Windows/macOS/Linux

the Windows .exe can not be compiled from sources under Linux, so this particular runtime can never be distributed on Debian official?


Debian contains cross-compilers for Windows (but not macOS yet), so you can compile a .exe and build that into a .deb easily.

https://packages.debian.org/search?keywords=mingw

Probably the right thing for you to do is switch to WinGet on Windows and the Apple Store for macOS.


moving from CGi to FastCGI is pretty easy



In Java you would use packages to group together class definitions

same as with C++, C# where you would use namespaces to do that

aka define the scope of classes

in AS3, the packages are used the same, group collection of definitions, not only classes and interfaces but also variables, constants.

The namespaces in AS3 are used to define the visibility of definitions at the class level, a bit like being able to define your own "public" attribute.

In ActionScript 3, by default the AS3 namespace is open, for example with a builtin like Array instead of using the push() method defined in the prototype, it uses the push() method defined in the AS3 namespace.

See https://github.com/adobe/avmplus/blob/master/core/Array.as#L...

But you also have mode to compile with -ES to not open that AS3 namespace by default.

In ES4, namespaces could do more advanced stuff like namespace shadowing (only a proposal at the time), see https://web.archive.org/web/20070629024201/http://developer....

For AS3, see 1.9 Namespaces / 12 Namespaces / etc. https://github.com/as3lang/ActionScript3/wiki/Specification


> The closest thing we had for ES4, was probably Flash Actionscript 3.

No.

Flash = a browser plugin

ActionScript 3 = a programming language

ActionScript 3 can run in other runtimes than just Flash

Adobe AIR is another runtime, target desktop (Windows, macOS) and mobile (iOS, Android).

Redtamarin is yet another runtime (based on the avmplus) target the command-line and server-side (Windows, macOS, Linux).


And yet a good part of ES4 been realistically implemented in ActionScript 3 and used by many developers for over a decade.

And those namespaces in AS3 (much simpler than in ES4) I think are quite a good idea, they allow to control what is visible or not and/or to switch which implementation you use.

For example when some AS3 builtins do not support some methods defined later in ES5.1 then ES6 etc.

    ES5 function trim():String
    ES6 function repeat(count:Number):String
So yeah you not gonna use namespaces everyday for everything, but they do have allow to solve specific problems while "programming in the large".


WebAssembly not gonna give you access to syscall that are simply not there in the Web API


Text metrics, the graphics engine implemented on top of WebGL/WebGPU does it itself.

Weak references are coming, https://github.com/tc39/proposal-weakrefs


no, I'm talking about this

[0] does support for socket(udp and tcp)? [1] encountered with problem when Porting UDP socket communication c code using emscripten

one example among other, and so you can use WebAssembly all you want you will never be able to implement flash.net.DatagramSocket

[0]: https://github.com/WebAssembly/design/issues/1251 [1]: https://github.com/emscripten-core/emscripten/issues/5196


Yes you can, polyfill using WebSockets.

It would require a server component as gateway, so what.


well that very same attack vector aka "visiting a web site" is what everyone had against Flash

how convenient to consider that "pretty slim" now


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: