vpavlov79 0 / 0 / 0 Регистрация: 24.08.2015 Сообщений: 7 |
||||||||
1 |
||||||||
24.08.2015, 09:50. Показов 7591. Ответов 14 Метки нет (Все метки)
P.S плохо с русским Парни кто может мне помочи….со строковыми константы вроде я чегота не понемаю Нижу приведу пример моего кода но вот както он не работает
Но выдаёт ошибку : Или так : что тоже ошибка ########## — 2
Код ошибки #2 ——————————- В чем проблема?
__________________
0 |
Jewbacabra 4839 / 3852 / 1598 Регистрация: 24.04.2014 Сообщений: 11,302 |
||||
24.08.2015, 09:58 |
2 |
|||
1 |
Velesthau 528 / 430 / 159 Регистрация: 25.11.2014 Сообщений: 1,662 |
||||||||
24.08.2015, 09:59 |
3 |
|||||||
В чем проблема? В том, что ты объявляешь массив char, а инициализировать пытаешься массивом указателей.
либо так:
1 |
vpavlov79 0 / 0 / 0 Регистрация: 24.08.2015 Сообщений: 7 |
||||
24.08.2015, 10:06 [ТС] |
4 |
|||
Velesthau,
Код ошибки так почему они говорят что работает
0 |
Velesthau 528 / 430 / 159 Регистрация: 25.11.2014 Сообщений: 1,662 |
||||
24.08.2015, 10:16 |
5 |
|||
так почему они говорят что работает Он компилируется, но предупреждает, что «тестовая строка» — это неизменяемая строка (string constant), а p в это коде — указатель на строку, которую компилятор считает, что можно менять. Потом получишься ошибку на стадии работы программы, если через p попытаешься поменять строку (например, сделаешь p[1] = ‘a’.
, то предупреждение должно уйти и при попытке поменять строку через p, ты увидишь ошибку еще на стадии компиляции, а не при запуске, что будет правильней, так как убережет от проблем во время запуска.
0 |
551 / 383 / 126 Регистрация: 02.10.2008 Сообщений: 1,564 Записей в блоге: 1 |
|
24.08.2015, 10:19 |
6 |
Компилер выдал предупреждение на неявное преобразование char* в const char*
0 |
528 / 430 / 159 Регистрация: 25.11.2014 Сообщений: 1,662 |
|
24.08.2015, 10:22 |
7 |
Компилер выдал предупреждение на неявное преобразование char* в const char* Наоборот должно быть сделать указатель константным — это частая практика, чтобы обезопасить себя от случайного изменения, и ошибкой не является.
0 |
vpavlov79 0 / 0 / 0 Регистрация: 24.08.2015 Сообщений: 7 |
||||||||
24.08.2015, 10:35 [ТС] |
8 |
|||||||
Velesthau,
Или Так
Вот как я понимаю эти два кода Но вот что значет эти все выражение разве * это не значет получять значение катори лежит по адресу 0x….;
0 |
528 / 430 / 159 Регистрация: 25.11.2014 Сообщений: 1,662 |
|
24.08.2015, 10:55 |
9 |
НО вотиногда некоторые пишут так При объявлении — нет, это не получать значение, а инициализировать указатель. Так же как через указатель должно же получаться менять значение, на которое указывает он. Так же через *p.
0 |
vpavlov79 0 / 0 / 0 Регистрация: 24.08.2015 Сообщений: 7 |
||||
24.08.2015, 11:11 [ТС] |
10 |
|||
Velesthau, Добавлено через 8 минут
При int также….
0 |
gazlan 3174 / 1933 / 312 Регистрация: 27.08.2010 Сообщений: 5,131 Записей в блоге: 1 |
||||
24.08.2015, 11:23 |
11 |
|||
Миниатюры
0 |
528 / 430 / 159 Регистрация: 25.11.2014 Сообщений: 1,662 |
|
24.08.2015, 11:40 |
12 |
то жто значет я инициарищировал укзатель *p со значением 2; Значит, указатель будет указывать на адрес 2.
тоесть выражение char a = &p; // вернет адрес где лежит двоика Если указатель p указывает на адрес 2, то да &p вернет адрес указателя. То есть, двойки, в случае если p=2.
0 |
0 / 0 / 0 Регистрация: 24.08.2015 Сообщений: 7 |
|
24.08.2015, 12:58 [ТС] |
13 |
Velesthau, а как насчет строк….char *p = «string»; что вернет в это случее указатель адрес string…тоесть адрес там где лежит это строка…..от этих указателеи у меня головокружение
0 |
528 / 430 / 159 Регистрация: 25.11.2014 Сообщений: 1,662 |
|
24.08.2015, 13:30 |
14 |
что вернет в это случее указатель адрес string…тоесть адрес там где лежит это строка Я не понял формулировки вопроса.
0 |
0 / 0 / 0 Регистрация: 24.08.2015 Сообщений: 7 |
|
24.08.2015, 15:27 [ТС] |
15 |
Velesthau,
0 |
При компиляции я получаю следующую ошибку:
Error: Too many initializers for 'char[26]'.
Я продолжаю получать эту ошибку, вы можете мне помочь с этим? Вот код
#include <iostream>
#include <fstream>
using namespace std;
int defunct();
int defunct(char a[], char b[], char c[]){
int d,l,s,m,mod;
mod = 47;
s = 1;
m = 0;
for(d = 0;d <= 6;d++){
for(l=0;l<=25;l++){
if (a[d] = c[l]){
s *= l + 1;
}
if (a[d] = ' '){
s *= l + 1;
}
}
}
for(d = 0;d <= 6;d++){
for(l=0;l<=25;l++){
if (b[d] = c[l]){
m *= l + 1;
}
if (b[d] = ' '){
m *= l + 1;
}
}
}
if ((s%mod)==(m%mod)){
cout << "GOn";
}
if ((s%mod)!=(m%mod)){
cout << "STAYn";
}
}
int main(){
int i;
char a[6], b[6];
char alphabet[26] = {"A", "B", "C", "D", "E", "F", "G", "H", "I", "J", "K", "L", "M", "N", "O", "P", "Q", "R", "S", "T", "U", "V", "W", "X", "Y", "Z"};
i = 0;
ofstream fout ("ride.out");
ifstream fin ("ride.in");
fin >> a >> b;
fout << defunct(a, b, alphabet);
return 0;
}
Что я должен сделать, чтобы избавиться от этой ошибки? Спасибо, я очень ценю вашу помощь.
-2
Решение
Вы создаете свой алфавит из строки вместо символов:
char alphabet[26] = {"A", "B", "C", "D", "E", "F", "G", "H", "I", "J", "K", "L", "M", "N", "O", "P", "Q", "R", "S", "T", "U", "V", "W", "X", "Y", "Z"};
Использование:
char alphabet[26] = {'A', 'B', 'C', /* etc. */};
3
Другие решения
Следующий фрагмент кода генерирует похожие ошибки:
#include <iostream>
int main()
{
char alphabet[1] = {"A","B"};
return 0;
}
- … main.cpp | 6 | ошибка: слишком много инициализаторов для ‘char [1]’
- … main.cpp | 6 | ошибка: строка инициализатора для массива символов слишком длинная
[-Fpermissive] | - … main.cpp | 6 | предупреждение: неиспользуемая переменная ‘alphabet’
[-Wunused-переменная] |
Сбой сборки: 2 ошибки, 1 предупреждение (0 минут, 7 секунд) === |
В вашем коде есть правильное количество мест для алфавита, но вы сохраняете два символа для каждого места. В моем коде у меня только одно местоположение, и я пытаюсь сохранить две «вещи».
«A» означает, что у вас есть строка с символами «A», за которой следует 0. Вам необходимо иметь два местоположения для их хранения. Теперь измените код на следующий:
char alphabet[2][2] = {"A","B"};
Если вы сделаете это, то останется только ошибка (3) выше. (Это только для объяснения)
Чтобы инициализировать символ, используйте одинарные кавычки. Иметь подходящее количество мест для хранения персонажей. Я надеюсь, что это помогает.
2
const byte frames_array[][259][1] = { { {255, 1, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {237, 28, 36}, {237, 28, 36}, {237, 28, 36}, {237, 28, 36}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {237, 28, 36}, {237, 28, 36}, {237, 28, 36}, {237, 28, 36}, {237, 28, 36}, {237, 28, 36}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {237, 28, 36}, {237, 28, 36}, {237, 28, 36}, {237, 28, 36}, {237, 28, 36}, {237, 28, 36}, {237, 28, 36}, {237, 28, 36}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {237, 28, 36}, {237, 28, 36}, {237, 28, 36}, {237, 28, 36}, {255, 242, 0}, {255, 242, 0}, {255, 242, 0}, {255, 242, 0}, {255, 242, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {255, 242, 0}, {255, 242, 0}, {255, 242, 0}, {255, 242, 0}, {255, 242, 0}, {0, 0, 0}, {255, 242, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {255, 242, 0}, {255, 242, 0}, {255, 242, 0}, {255, 242, 0}, {255, 242, 0}, {255, 242, 0}, {255, 242, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {255, 242, 0}, {255, 242, 0}, {255, 242, 0}, {255, 242, 0}, {255, 242, 0}, {255, 242, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {255, 242, 0}, {255, 242, 0}, {255, 242, 0}, {255, 242, 0}, {255, 242, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {63, 72, 204}, {63, 72, 204}, {63, 72, 204}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {63, 72, 204}, {63, 72, 204}, {63, 72, 204}, {63, 72, 204}, {63, 72, 204}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {63, 72, 204}, {63, 72, 204}, {63, 72, 204}, {63, 72, 204}, {63, 72, 204}, {63, 72, 204}, {63, 72, 204}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {63, 72, 204}, {0, 0, 0}, {63, 72, 204}, {63, 72, 204}, {63, 72, 204}, {0, 0, 0}, {63, 72, 204}, {63, 72, 204}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {255, 242, 0}, {0, 0, 0}, {0, 0, 0}, {63, 72, 204}, {63, 72, 204}, {63, 72, 204}, {0, 0, 0}, {0, 0, 0}, {255, 242, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {63, 72, 204}, {0, 0, 0}, {63, 72, 204}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {63, 72, 204}, {0, 0, 0}, {63, 72, 204}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {63, 72, 204}, {63, 72, 204}, {63, 72, 204}, {0, 0, 0}, {63, 72, 204}, {63, 72, 204}, {63, 72, 204}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0}, {0, 0, 0} } };
У меня снова проблема, необходимо инициализировать массив с картинкой для лед дисплея, а потом использовать, но выходит это
Arduino: 1.8.16 (Windows 10), Плата:»Arduino Uno»
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
};
^
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
picture:264:3: error: too many initializers for ‘const byte [1] {aka const unsigned char [1]}’
exit status 1
too many initializers for ‘const byte [1] {aka const unsigned char [1]}’