module

问题 I am a bit confused, about how to require and use modules in Node.js. My scenario is the following: I wrote a complete server in one single file, which uses Socket.io for realtime communication. Now the index.js became pretty big, and I want to split the code into several modules to make it more managable. For example I have some functions for serving a Survey to the clients, and getting back their answers. I put all those functions in a seperate module, and require it in the index.js. Works

问题 I am doing some tests with Ruby 2.7.1 on FreeBSD 12.1. I know how to extend a class with module with for instance this : class Myclass def mymethod extend Mymodule end end But is it possible to obtain the same result with something that looks like this : class Myclass def mymethod var = "Mymodule" extend var end end If I do this like that, I off-course obtain an error, since extend is pointing to a string and not a module. Here are some explanations - it would be useful in the following

问题 I have a simple file types.ts that defines some types: export interface MyInterface { // ... } export const enum MyEnum { // ... } export type MyType = { // ... } I have read about the new feature import type for the latest typescript here. As far as I understand it is meant to fix specific problems which seems mostly to happen when importing from .js files. I can import my types with both import and import type statements. Both seems to work equally fine. The question is should I prefer

问题 I have a simple file types.ts that defines some types: export interface MyInterface { // ... } export const enum MyEnum { // ... } export type MyType = { // ... } I have read about the new feature import type for the latest typescript here. As far as I understand it is meant to fix specific problems which seems mostly to happen when importing from .js files. I can import my types with both import and import type statements. Both seems to work equally fine. The question is should I prefer

问题 I have a simple file types.ts that defines some types: export interface MyInterface { // ... } export const enum MyEnum { // ... } export type MyType = { // ... } I have read about the new feature import type for the latest typescript here. As far as I understand it is meant to fix specific problems which seems mostly to happen when importing from .js files. I can import my types with both import and import type statements. Both seems to work equally fine. The question is should I prefer

问题 My question is dedicated mostly to profs and is about using C++ in "strange" way. In C++ there isn't really big difference between pointers to variables and pointers to functions. We can do something useless like this: char* buff = new char[32]; void (*func)() = (void (*)())buff; But we allmost created a function that never existed, right? What if we go further and fill buff with x86 commands stord in a file? OS will never know that a function was created. #include <iostream> using namespace

问题 My question is dedicated mostly to profs and is about using C++ in "strange" way. In C++ there isn't really big difference between pointers to variables and pointers to functions. We can do something useless like this: char* buff = new char[32]; void (*func)() = (void (*)())buff; But we allmost created a function that never existed, right? What if we go further and fill buff with x86 commands stord in a file? OS will never know that a function was created. #include <iostream> using namespace

问题 I have some custom .d.ts files and I want tsc to pick up these files when compiling. In order to get this done I modify the tsconfig.file to include the following "typeRoots": [ "../node_modules/@types", "./app/modules" ] ./app/modules is where my custom .d.ts file resides. Inside the ./app/modules folder I have the following file myModule.d.ts export declare module myModule { function Login(); function Logout(); } Now inside my other typescript file I have the following import import {

问题 I'm a beginner to advanced PowerShell techniques. I'm attempting to write my own PS module. Hopefully I can properly articulate my problem. Background: I've created a module of all of my commonly used functions, called MyTools . The PSM1 file simply dot sources other PS1 files in the same module folder. At the end of the module, I export the module members with Export-ModuleMember -Function * -Alias * -Cmdlet * . (I've also created a manifest, but I'm not sure that matters for my problem.)

问题 I'm trying to load the home page of my app for visitors who are not authenticated. const routes: Routes = [ { path: '', loadChildren: './home/home.module#HomeModule' } ... Authenticated users should get their feed via that module, also on the empty path. { path: '', loadChildren: './feed/feed.module#FeedModule', canActivate: [IsAuthenticationGuard] }, { path: '', loadChildren: './home/home.module#HomeModule', canActivate: [NoAuthenticationGuard] }, I would expect that IsAuthenticationGuard