tw39124-1

Results 7 comments of tw39124-1

Inline keyword call syntax

Re the suggested syntax, I definitely think the inner keyword should be enclosed within the variable-like syntax of `${xxx}` , because you are _substituting_ the argument to the outer keyword...

Inline keyword call syntax

> and there's no way it could be differentiated from normal variable usage. If we want to use the variable syntax, we need to use something like ´${[InnerKeyword]}`. Yes good...

Allow resource files and libraries to be imported privately in other resource files

Already addressed by #430

USB_RAW_IOCTL_EP_READ/USB_RAW_IOCTL_EP_WRITE maximum length = PAGE_SIZE

Thanks for the quick reply. I've tested it out by removing the PAGE_SIZE check altogether, recompiling the module, and it seems to work with larger IO sizes (I tried 8KB...

USB_RAW_IOCTL_EP_READ/USB_RAW_IOCTL_EP_WRITE maximum length = PAGE_SIZE

After further debugging it looks like `dummy_hcd.c` has this block, in the `transfer()` function: ``` ... if (req->req.length == req->req.actual) { if (req->req.zero && to_host) rescan = 1; else req->req.status...

WITH NAME should create a new instance regardless of arguments or library scope

Any thoughts on this issue?

WITH NAME should create a new instance regardless of arguments or library scope

@pekkaklarck Thanks for the response. I think the use case I outlined above pretty much sums up the situation. If you have a library which is implemented as a Python...