Rushi98

Rushi98

// BINARY  SEARCH TREE


#include<stdio.h>
#include<stdlib.h>
#include <stdbool.h> // bool

struct node
{
  int ele;

Rushi98

#include <stdio.h>

char s[] = {
	'\t',
	'0',
	'\n',
	'}',
	';',
	'\n',
	'\n',

Rushi98

#include <stdio.h>

char s[] = {
	9,
	48,
	10,
	125,
	59,
	10,
	10,

Rushi98

Note that if you're using version 1.9.0 or earlier please refer to the legacy documentation.

REST Assured is a Java DSL for simplifying testing of REST based services built on top of HTTP Builder. It supports POST, GET, PUT, DELETE, OPTIONS, PATCH and HEAD requests and can be used to validate and verify the response of these requests.

Contents

1. Static imports
2. Examples
   1. JSON Example
   2. JSON Schema Validation
3. XML Example

Rushi98

rsync                                                          \
 --verbose                                                     \
 --human-readable                                              \
 --itemize-changes                                             \
 --recursive                                                   \
 --archive                                                     \
 /Users/rushikesh/Documents                                    \
 /Volumes/New\ Volume/backup/

Rushi98

/**
 * Note: The returned array must be malloced, assume caller calls free().
 */
int* grayCode(int n, int* returnSize) {
    int size = 1 << n; // 2 ^ n
    int *sequence = (int *) calloc(size, sizeof(int));
    
    sequence[0] = 0;

Rushi98

gs -q -sPAPERSIZE=a4 -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=<output.pdf> <list-of-input.pdf>

Rushi98

//Contents from https://spring.io/understanding/CORS

In the simplest scenario, cross-origin communications starts with a client making a GET, POST, or HEAD request against a resource on the server. In this scenario, the content type of a POST request is limited to application/x-www-form-urlencoded, multipart/form-data, or text/plain. The request includes an Origin header that indicates the origin of the client code.

The server will consider the request's Origin and either allow or disallow the request. If the server allows the request, then it will respond with the requested resource and an Access-Control-Allow-Origin header in the response. This header will indicate to the client which client origins will be allowed to access the resource. Assuming that the Access-Control-Allow-Origin header matches the request's Origin, the browser will allow the request.

On the other hand, if Access-Control-Allow-Origin is missing in the response or if it doesn't match the request's Origin, the browser will disallow th

Rushi98

[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.10.107-lineageos-gb040571 (jenkins@agrippa.acc.umu.se) (gcc version 4.9 20150123 (prerelease) (GCC) ) #1 SMP PREEMPT Sun Mar 25 13:20:18 CEST 2018
[    0.000000] CPU: AArch64 Processor [410fd031] revision 1
[    0.000000] Machine: Qualcomm Technologies, Inc. MSM 8939 CP8675
[    0.000000] cma: Found external_image__region@0, memory base 0x0000000086000000, size 8 MiB, limit 0xffffffffffffffff
[    0.000000] cma: Found modem_adsp_region@0, memory base 0x0000000086800000, size 86 MiB, limit 0xffffffffffffffff
[    0.000000] cma: Found pheripheral_region@0, memory base 0x000000008be00000, size 6 MiB, limit 0xffffffffffffffff
[    0.000000] cma: Found mba_region@0, memory base 0x0000000000000000, size 2 MiB, limit 0xffffffffffffffff