... you are back to trying to entertain all of us with your foolishness but this type of stupidity just is NOT worth even a minimal laff. -- I'm an opinionated bastard. Everything I post is my opinion. If you do not like my opinions then killfile me - if you like my opinions then send ...
...Dear Tony Bowden, This is a computer-generated report for Bit-Vector-Minimal-1.3 on perl 5.10.0, created by CPAN-Reporter-...games:/home/devogon/bin:/usr/games/bin:/usr/bin/mh:/usr/local/everything/bin:/usr/lib/surfraw:/home/devogon/bin:/usr/games/bin:/usr/bin/mh:/usr/local/everything/bin:/usr/lib/surfraw PERL5LIB = PERL5_CPANPLUS_IS_RUNNING = 7131 PERL5_CPAN_IS_RUNNING = 7131...
...to prevent any duplicate effort. -- Dear Tony Bowden, This is a computer-generated report for Bit-Vector-Minimal-1.3 on perl 5.10.0, created by CPAN-Reporter-1.11. Thank you for uploading .../local/bin:/usr/bin:/bin:/usr/games:/home/d/bin:/usr/games/bin:/usr/bin/mh:/usr/local/everything/bin PERL5LIB = /home/d/.cpan/build/Tie-Array-Sorted-1.41-WkWGIj/blib/arch:/home/d/.cpan/build/...
...(Unmanaged C.) Some have a large heap. (Managed C, Java, etc.) Some put everything in the heap, including the call stack. (Some more exotic language implementations.) ...for many cases, they usually opted for doing one thing reasonably well and neglecting everything else (regularly drawing flame from those parties who happened to need some of that "everything else" stuff). Regards, Jo
...m not yet convinced of). My purpose was to figure out a way of implementating extended file attributes with minimal disruption to the usual Unix/Plan 9 file model. Note that the Linux/Solaris-10 (Posix?) ... symlinks, which I detest. ... Yes, the analogy is close. but they broke just about everything by introducing a second kind of file. ... Which is what we want to avoid this time....
... madness that we're currently using even though we're coding in Python. Mnesia is quite lightweight from what I have read. It can be because it's optimized for keeping everything in memory. Erlang is designed for perpetual processes, so the database need not be efficient for those operations that make the data persistent. Of course, Mnesia also eliminates the impedance mismatch. (The ...
...> Maybe we need some faster type of IPC, like x86 call gates directly between user processes, instead of using sockets and system calls. Everything is possible. But (1) if it is processor dependent it won't port efficiently to other architectures and (2) AFAIR x86 call gates are everything but fast :-). Regards -- Markus
... by using an anonymous memory-mapped area for the heap, then copy-on-write mapping it in the new process. Yes, certainly. It requires one to actually change the language runtime a good bit. Then everything is possible. I'm refreining from adding "But ..." since I'm sure you can fill in that part for yourself. Emulating what fork() does in user space is just not as efficient as a fork() ...
... macro is called, the Lisp system enters a "macro world," so naturally everything in that world must be defined using defmacro. This is the wrong...with "but there *are* some pretty important differences"; in my eyes, Lisp minimizes the differences that can be minimized, but some differences cannot be eliminated - and I still think that the additional programmer-visible complexity is a ...
... variant quotation mechanism in Lisp, you can just implement it as a macro! Yeah, yeah, thanks. I'm sure, Jon is absolutely enraptured. Probably this is the very thing he has been hoping for. Next week will see him doing everything in Lisp from now on. One possible explanation for this mistake may be that in other "this mistake" => The mistake none of us made. Regards -- Markus
